Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: d3c53d308e88570495fae9e0243b944701a9b5dfa754a89dd143ef8b933392b7 Tx public key: 2d5a399016c8d0a61b2527c9a0f29345b456728bc6efbe48aab9cbf5ebaf4916 Payment id (encrypted): 2b5d7bf23f0e2be1
Timestamp: 1620124668 Timestamp [UCT]: 2021-05-04 10:37:48 Age [y:d:h:m:s]: 00:006:13:25:37
Block: 691750 Fee (per_kB): 1.26 (0.10) Tx size: 13.1934 kB
Tx version: 2 No of confirmations: 4731 RingCT/type: yes/3
Extra: 012d5a399016c8d0a61b2527c9a0f29345b456728bc6efbe48aab9cbf5ebaf49160209012b5d7bf23f0e2be1

2 output(s) for total of ? upx

stealth address amount amount idx
00: 5a3ce6f05fcb3e5d1160cfb5c6bb594837372e777764701600f0f0d3fa03328a ? 3461178 of 3489515
01: 80e874b605bf87f5d840a5ec2aed026b580d2ada9f898b2c0e3508a92ab6a92a ? 3461179 of 3489515

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: