Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: ebfd6d447e6abd00c9a2265400925e192be4bd96a789074e26c76d6ce8c11fa2 Tx public key: 2875e57b3c4cb151c3ce9c8cb7ad0791f1558a87dc8a99d5b66c006f1f08701c
Timestamp: 1547256911 Timestamp [UCT]: 2019-01-12 01:35:11 Age [y:d:h:m:s]: 04:326:15:31:23
Block: 84540 Fee (per_kB): 2.70 (1.03) Tx size: 2.6289 kB
Tx version: 2 No of confirmations: 1286016 RingCT/type: yes/3
Extra: 012875e57b3c4cb151c3ce9c8cb7ad0791f1558a87dc8a99d5b66c006f1f08701c

2 output(s) for total of ? upx

stealth address amount amount idx
00: d474657abf53e4c4c0e2b55902b9b4b2587e97925b4e4c4566aa2f4830dcf2e4 ? 239599 of 5948315
01: a680aba327e463246b913d8a18f5c02a18c70d9a3faeeb9020045ece2d22024d ? 239600 of 5948315

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: 0.2.2.0-45887ac92