Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: be35b45de5425371f523c27d4d9c32240fc337a26678f8e1f89b15a441080f4f Tx public key: 377a3ec798ce323ce6930ae9b4a198028df853cd5919df7b7dc66d245abc686c Payment id (encrypted): 6bb91e4553bddf9c
Timestamp: 1626929241 Timestamp [UCT]: 2021-07-22 04:47:21 Age [y:d:h:m:s]: 00:010:21:22:04
Block: 748476 Fee (per_kB): 0.08 (0.04) Tx size: 1.8359 kB
Tx version: 2 No of confirmations: 7822 RingCT/type: yes/3
Extra: 01377a3ec798ce323ce6930ae9b4a198028df853cd5919df7b7dc66d245abc686c0209016bb91e4553bddf9c

2 output(s) for total of ? upx

stealth address amount amount idx
00: 6eec80ff7f78e4ed060261faecfef147f9e28fb20ad368a80ac1f1c66bad83f0 ? 3760743 of 3794074
01: 71ca23864bb11d4f186a9c0c85127a2f5050cb67125812b90b6514fdf06aa66b ? 3760744 of 3794074

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: