uPlexa Block Explorer

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

Tx hash: 6889e49692453c55e860eaeff437d080a930da5dd652c6371b57aa8feb56b27b

Tx prefix hash: 5c4f311a47a26c25fa07a70af69362e71f284f4972d601c22ccd7b7495b60ae8
Tx public key: 4d013fdf87fc35555b08f9d2f8b6060ba81b3db340f583c482870c06549e345e
Timestamp: 1605991975 Timestamp [UCT]: 2020-11-21 20:52:55 Age [y:d:h:m:s]: 00:011:13:07:23
Block: 573985 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 8323 RingCT/type: yes/0
Extra: 014d013fdf87fc35555b08f9d2f8b6060ba81b3db340f583c482870c06549e345e02110000000b126a7f00000000010000071400

1 output(s) for total of 1915.98 upx

stealth address amount amount idx
00: 9bac5df0110645421765fa7dc57db162943b8355a95b1f1c4924f926d02b5a1b 1915.98 2965485 of 0

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



{ "version": 2, "unlock_time": 574045, "vin": [ { "gen": { "height": 573985 } } ], "vout": [ { "amount": 191598, "target": { "key": "9bac5df0110645421765fa7dc57db162943b8355a95b1f1c4924f926d02b5a1b" } } ], "extra": [ 1, 77, 1, 63, 223, 135, 252, 53, 85, 91, 8, 249, 210, 248, 182, 6, 11, 168, 27, 61, 179, 64, 245, 131, 196, 130, 135, 12, 6, 84, 158, 52, 94, 2, 17, 0, 0, 0, 11, 18, 106, 127, 0, 0, 0, 0, 1, 0, 0, 7, 20, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2019-01-05-0432f03 (1.1) | uPlexa version: 0.2.0.2-release