Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: d418191d984706417bdc65f5c05216ce08775391d0b0e4bed99c09b7127af118 Tx public key: c9c0ff03d0ddfecae59d80c75649a9cf8f5f41756a2eeddea8cc8cafd22cd530 Payment id (encrypted): 938873081ff53c3f
Timestamp: 1546464228 Timestamp [UCT]: 2019-01-02 21:23:48 Age [y:d:h:m:s]: 04:338:00:38:33
Block: 77884 Fee (per_kB): 2.70 (1.02) Tx size: 2.6465 kB
Tx version: 2 No of confirmations: 1294273 RingCT/type: yes/3
Extra: 020901938873081ff53c3f01c9c0ff03d0ddfecae59d80c75649a9cf8f5f41756a2eeddea8cc8cafd22cd530

2 output(s) for total of ? upx

stealth address amount amount idx
00: dbc5b6f4ca6d5e6e9a772c00481443a02225150b01cbfb68f736e05ae583c483 ? 203804 of 5953847
01: 6aeb5bd7a78866674b11f62d2b74614f6439be457193114830bf7941e52b4b18 ? 203805 of 5953847

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: