Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 7aec982dc4d26bb08124dd6aa9c7dfd1cc2c4526848b9ee9909a4d07b692d735 Tx public key: abd2ed5125397357c0d32d7335e37fe1e0cc264b44d2598db155a87a4e39cd71 Payment id (encrypted): ca0241036eebded7
Timestamp: 1634175465 Timestamp [UCT]: 2021-10-14 01:37:45 Age [y:d:h:m:s]: 00:009:14:53:00
Block: 808817 Fee (per_kB): 0.08 (0.04) Tx size: 1.8369 kB
Tx version: 2 No of confirmations: 6939 RingCT/type: yes/3
Extra: 01abd2ed5125397357c0d32d7335e37fe1e0cc264b44d2598db155a87a4e39cd71020901ca0241036eebded7

2 output(s) for total of ? upx

stealth address amount amount idx
00: d87cf8c91a6cc622dd606edf84806c87826dd88cfc9a9a9e818494f034db5ed4 ? 3995980 of 4025168
01: 18bea8bd4ed551e60b4dbdd0aaa0598be0f03f610c6d070402e7412962b26912 ? 3995981 of 4025168

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: