Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 52f30f762d766484b0c8debe8d33c4a83d0ab7900b52055424db18c24c29c098 Tx public key: ced920d09c8d18529aac6b851f905a1c990f182da31c5c90c9f636c7df4b5b5f
Timestamp: 1546460486 Timestamp [UCT]: 2019-01-02 20:21:26 Age [y:d:h:m:s]: 04:338:00:57:14
Block: 77860 Fee (per_kB): 1.80 (0.99) Tx size: 1.8242 kB
Tx version: 2 No of confirmations: 1294266 RingCT/type: yes/3
Extra: 01ced920d09c8d18529aac6b851f905a1c990f182da31c5c90c9f636c7df4b5b5f

2 output(s) for total of ? upx

stealth address amount amount idx
00: f4203f2fe003bf62eb7b4ce470c4f231637034d071fc721c315c368d8cee1dd0 ? 203618 of 5953759
01: dba13a563abfd6ba85ee917cfd6fadc691c86267c1a6a3c24d79439fba79d607 ? 203619 of 5953759

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