Uplexa Block Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)


Autorefresh is OFF
Tx hash: 29c2be63cf47c822cf9dde9cc275e6bf1b3b27ea1e1534ddf4aed466b170b365 Tx public key: 56220aae887eea793607e14e807b1acb48c5f490f44154255aa0056cb733bf9e Payment id (encrypted): 0c9119c8a0fa08ec
Timestamp: 1659747112 Timestamp [UCT]: 2022-08-06 00:51:52 Age [y:d:h:m:s]: 00:012:09:11:31
Block: 1021871 Fee (per_kB): 0.56 (0.04) Tx size: 13.1621 kB
Tx version: 2 No of confirmations: 8916 RingCT/type: yes/3
Extra: 0209010c9119c8a0fa08ec0156220aae887eea793607e14e807b1acb48c5f490f44154255aa0056cb733bf9e

2 output(s) for total of ? upx

stealth address amount amount idx
00: f10a0f8be380d381878299b5be2d6536ca185f28b0d8ef1deea4cb5f40302f50 ? 4854876 of 4890197
01: 99822fa8398547f47f94fa6b0e72d45bfecd07a7fc8e00915640e6cbfae867d9 ? 4854877 of 4890197

Check which outputs belong to given uPlexa address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side

Prove to someone that you have sent them uPlexa in this transaction

Tx private key can be obtained using get_tx_key command in uplexa-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side

source code | explorer version (api): master-2019-01-05-0432f03 (1.1) | uPlexa version: