Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 83989491283dbfe403c3e58fcec80002baba46df0c466ccf3a24f3527ae2c281 Tx public key: 23b4e5651317a15530c580a380f0312639cce695b4f17d646429dfa901614ac8 Payment id (encrypted): 5038021b7eaa71ec
Timestamp: 1617913652 Timestamp [UCT]: 2021-04-08 20:27:32 Age [y:d:h:m:s]: 00:005:01:26:54
Block: 673299 Fee (per_kB): 0.08 (0.04) Tx size: 1.8389 kB
Tx version: 2 No of confirmations: 3640 RingCT/type: yes/3
Extra: 0123b4e5651317a15530c580a380f0312639cce695b4f17d646429dfa901614ac80209015038021b7eaa71ec

2 output(s) for total of ? upx

stealth address amount amount idx
00: 8e2ac555a8db4f8eaec2da7de651650ca0693a96c5715e5a08c97f2eafbd7b1a ? 3352796 of 3370661
01: bb570ecc0a93f93f47390034a4aec049fbee625fc08c5500cca77e47a9233e48 ? 3352797 of 3370661

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: