Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: d8ba01250f632634e1686c2d22c31730c62a57a5c536e0defeb6604a40b0171f Tx public key: c754fd98a6719fa8b15cdb293b614fffdcefebc3e3cb99dd59c5f0abc886141c Payment id (encrypted): fd55bbec51e7637f
Timestamp: 1623363181 Timestamp [UCT]: 2021-06-10 22:13:01 Age [y:d:h:m:s]: 00:008:17:47:28
Block: 718729 Fee (per_kB): 0.24 (0.05) Tx size: 5.0732 kB
Tx version: 2 No of confirmations: 6306 RingCT/type: yes/3
Extra: 01c754fd98a6719fa8b15cdb293b614fffdcefebc3e3cb99dd59c5f0abc886141c020901fd55bbec51e7637f

2 output(s) for total of ? upx

stealth address amount amount idx
00: a4da8ae446889b793196b7b41d84e253b306447ce90b94eabca1ffeba16fdada ? 3613586 of 3646119
01: 7320408491c673b66ff0e8e3fb98e781833908d74c3d084d157c485e23c6d9c8 ? 3613587 of 3646119

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: