uPlexa Block Explorer

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

Tx hash: f33fae2968d6ae27ac9dc12b896120810c117258a9b9d0430d7abc915ce0622c

Tx prefix hash: 7b707c1b5b9b7e74a07f68e8806109154cd5a9549cb4b8b32308857a8e1a02b4
Tx public key: c814d5ca03ebe910c85319b669ecedbf1afe768e47205f4449f1ddb5dd6dbe03
Timestamp: 1585193898 Timestamp [UCT]: 2020-03-26 03:38:18 Age [y:d:h:m:s]: 00:014:08:03:44
Block: 400604 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 10320 RingCT/type: yes/0
Extra: 01c814d5ca03ebe910c85319b669ecedbf1afe768e47205f4449f1ddb5dd6dbe030211000000077d7e0d00000000000000000000

1 output(s) for total of 1997.40 upx

stealth address amount amount idx
00: e2f5f47bc94385fa2404d6c1e691fd0906a0b409c0a67dd4c6cbe2695f39ff79 1997.40 2223518 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": 400664, "vin": [ { "gen": { "height": 400604 } } ], "vout": [ { "amount": 199740, "target": { "key": "e2f5f47bc94385fa2404d6c1e691fd0906a0b409c0a67dd4c6cbe2695f39ff79" } } ], "extra": [ 1, 200, 20, 213, 202, 3, 235, 233, 16, 200, 83, 25, 182, 105, 236, 237, 191, 26, 254, 118, 142, 71, 32, 95, 68, 73, 241, 221, 181, 221, 109, 190, 3, 2, 17, 0, 0, 0, 7, 125, 126, 13, 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