Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 5e4a2d11e831bd3a1d1a223d0e72f622e489cd80857526a172a68689466b3069 Tx public key: 608ea6e2ae5fec4bfc87ff655d93fb3b5e8790fa880a5d1b61002f6f74dbf097
Timestamp: 1685971361 Timestamp [UCT]: 2023-06-05 13:22:41 Age [y:d:h:m:s]: 00:108:06:37:55
Block: 1240253 Fee (per_kB): 0.12 (0.05) Tx size: 2.6309 kB
Tx version: 2 No of confirmations: 77865 RingCT/type: yes/3
Extra: 01608ea6e2ae5fec4bfc87ff655d93fb3b5e8790fa880a5d1b61002f6f74dbf097

2 output(s) for total of ? upx

stealth address amount amount idx
00: bb3a2f217024fa3765d9080d3ad4c58fbfef0d16aea8777377478cd55cfd30b4 ? 5548335 of 5773562
01: c87b4b9a086c1b90838437e4c15e7ab2b8b6e1ca3fc19a15258f4a31b8ffc6c0 ? 5548336 of 5773562

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: 0.2.2.0-45887ac92