Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 8b351acde3665e1e7070a09a672164480e24d6dc5345c7e4cb67bbffb6020e87 Tx public key: 65a4b31c28e5d2d74873891b2b507de21587e5efb96539570edf880f012ec34a Payment id (encrypted): fa881ce29da6c4e5
Timestamp: 1685971361 Timestamp [UCT]: 2023-06-05 13:22:41 Age [y:d:h:m:s]: 00:108:06:28:43
Block: 1240253 Fee (per_kB): 0.08 (0.04) Tx size: 1.8369 kB
Tx version: 2 No of confirmations: 77856 RingCT/type: yes/3
Extra: 0165a4b31c28e5d2d74873891b2b507de21587e5efb96539570edf880f012ec34a020901fa881ce29da6c4e5

2 output(s) for total of ? upx

stealth address amount amount idx
00: d3cb5d9a4545d40e5f4e6829fefff322ae7e96bfb7748ad8a702b87f10f4bd10 ? 5548339 of 5773528
01: 84c84406f4c9e0f7efec86e83296341e75773a100cfb5784a62a1d80a10154f9 ? 5548340 of 5773528

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: