Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 19b974c4a6630963c26509408e4a7ad0a2fe1f3786a7303078d7150e8fbb1531 Tx public key: 3acb6df2be07aa8543a29ec99e703c7ecf2a54f6466f923e3ccef7f59959ac61
Timestamp: 1685968290 Timestamp [UCT]: 2023-06-05 12:31:30 Age [y:d:h:m:s]: 00:108:05:30:19
Block: 1240226 Fee (per_kB): 0.00 (0.00) Tx size: 0.1318 kB
Tx version: 2 No of confirmations: 77834 RingCT/type: yes/0
Extra: 013acb6df2be07aa8543a29ec99e703c7ecf2a54f6466f923e3ccef7f59959ac6102110000000173de26710000000000000000000321004cbdf58c1d64331f0a888eb1a5bbd7385dd3dee36f03dbdb7f6daaf21ccb6804

1 output(s) for total of 1634.58 upx

stealth address amount amount idx
00: fb68f91c16e6c5862bbe4c2ebe4afcaf29713f0d01bb23d7b6d339987ab1c939 1634.58 5548263 of 0

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: