uPlexa Block Explorer

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

Tx hash: 0883a7995e4e228f15230b759e66b736fd4fdb1de70affdf7a790442d1d1b635

Tx prefix hash: 3246be1a455c012b767336e3e9d4247c9c1853b807626bdd02826e7c57184cd0
Tx public key: 381d6121b5b491b09b29d683076a57f0db880ae25b49cbeb1d2eddeb4b24c7d8
Timestamp: 1602972947 Timestamp [UCT]: 2020-10-17 22:15:47 Age [y:d:h:m:s]: 00:007:06:05:30
Block: 548849 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 5243 RingCT/type: yes/0
Extra: 01381d6121b5b491b09b29d683076a57f0db880ae25b49cbeb1d2eddeb4b24c7d802110000005029c0ef00000000000000000000

1 output(s) for total of 1927.49 upx

stealth address amount amount idx
00: 19b44987217aa52dda4a702f33113b4c90158173232059db7cefac3feaf2aa4e 1927.49 2871437 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": 548909, "vin": [ { "gen": { "height": 548849 } } ], "vout": [ { "amount": 192749, "target": { "key": "19b44987217aa52dda4a702f33113b4c90158173232059db7cefac3feaf2aa4e" } } ], "extra": [ 1, 56, 29, 97, 33, 181, 180, 145, 176, 155, 41, 214, 131, 7, 106, 87, 240, 219, 136, 10, 226, 91, 73, 203, 235, 29, 46, 221, 235, 75, 36, 199, 216, 2, 17, 0, 0, 0, 80, 41, 192, 239, 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