uPlexa Block Explorer

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

Tx hash: a29e3bd5a5b2cc540b5eba485f1981c810ec428e31c96da1b39f187297320748

Tx prefix hash: 3d599dedc855e01429e7a86bcfbca754ad65167ce7d4b941df29a3b02405c9c7
Tx public key: 42813a4fe320f987d9b0d582d4da406a4624fe87a263ace136cb9a7a13fc7c0c
Timestamp: 1614073652 Timestamp [UCT]: 2021-02-23 09:47:32 Age [y:d:h:m:s]: 00:002:10:11:54
Block: 641306 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 1713 RingCT/type: yes/0
Extra: 0142813a4fe320f987d9b0d582d4da406a4624fe87a263ace136cb9a7a13fc7c0c0211000000144f170b00000000000000000000

1 output(s) for total of 1889.03 upx

stealth address amount amount idx
00: 580908eb3e31963d3437a2293ee230c1cbbc0f2efc9699bcb2693a76d765a0b7 1889.03 3199783 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": 641366, "vin": [ { "gen": { "height": 641306 } } ], "vout": [ { "amount": 188903, "target": { "key": "580908eb3e31963d3437a2293ee230c1cbbc0f2efc9699bcb2693a76d765a0b7" } } ], "extra": [ 1, 66, 129, 58, 79, 227, 32, 249, 135, 217, 176, 213, 130, 212, 218, 64, 106, 70, 36, 254, 135, 162, 99, 172, 225, 54, 203, 154, 122, 19, 252, 124, 12, 2, 17, 0, 0, 0, 20, 79, 23, 11, 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