uPlexa Block Explorer

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

Tx hash: 5667e758c6cd140ef93ddca10a90953f66733814df431d5d475c066d414f93d6

Tx prefix hash: 993b94e98bbbc645332df23138d0d1959fc93bd47c85ef5fe4a59db3294b25bf
Tx public key: 72e7a766f108716e52a0af7811caff76840edc3cae3a3e9f5b81ca7e8a228703
Timestamp: 1593490033 Timestamp [UCT]: 2020-06-30 04:07:13 Age [y:d:h:m:s]: 00:002:04:41:04
Block: 469756 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 1593 RingCT/type: yes/0
Extra: 0172e7a766f108716e52a0af7811caff76840edc3cae3a3e9f5b81ca7e8a228703021100000004da346200000000000000000000

1 output(s) for total of 1964.19 upx

stealth address amount amount idx
00: 0bef0c32b5e2975e0cc38eb4190807b8a659412cd79995b060c4869c8e189b2b 1964.19 2531971 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": 469816, "vin": [ { "gen": { "height": 469756 } } ], "vout": [ { "amount": 196419, "target": { "key": "0bef0c32b5e2975e0cc38eb4190807b8a659412cd79995b060c4869c8e189b2b" } } ], "extra": [ 1, 114, 231, 167, 102, 241, 8, 113, 110, 82, 160, 175, 120, 17, 202, 255, 118, 132, 14, 220, 60, 174, 58, 62, 159, 91, 129, 202, 126, 138, 34, 135, 3, 2, 17, 0, 0, 0, 4, 218, 52, 98, 0, 0, 0, 0, 0, 0, 0, 0, 0, 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