Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: f6b70b1d394526937cd2ad1df631d9ecdf84778ac2cd6ecea02b110d0b390f58 Tx public key: c93c25b8f371eef764998828df9381d62a9546a80c2250349b90347f31fce88e Payment id (encrypted): 2fcb67bfc3ac5698
Timestamp: 1617913606 Timestamp [UCT]: 2021-04-08 20:26:46 Age [y:d:h:m:s]: 00:005:02:27:40
Block: 673298 Fee (per_kB): 1.26 (0.10) Tx size: 13.1797 kB
Tx version: 2 No of confirmations: 3665 RingCT/type: yes/3
Extra: 01c93c25b8f371eef764998828df9381d62a9546a80c2250349b90347f31fce88e0209012fcb67bfc3ac5698

2 output(s) for total of ? upx

stealth address amount amount idx
00: 89cc66d615ddde60c282fc2ea2a6e75ccd6f74f75021fc2ac41b9c9de69ddedd ? 3352767 of 3370781
01: 70e1221a6d73672b9cf5b291747550f3b131579b2a07a530523ee9f9937fccdf ? 3352768 of 3370781

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: