uPlexa Block Explorer

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

Tx hash: 88ad5f57ac208d82c865f386f0012074457399ab915eda7a6ff4267a295c1a41

Tx prefix hash: bc218d13f15b823f2611fa08a2476e6a2ada09612b6a9a490880386b776417c6
Tx public key: 8c15ab6e65226eb3d4141616a063cdb9b9213ebd25dd36b12085dcf2b7320fb7
Timestamp: 1600240432 Timestamp [UCT]: 2020-09-16 07:13:52 Age [y:d:h:m:s]: 00:005:01:29:36
Block: 526094 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 3636 RingCT/type: yes/0
Extra: 018c15ab6e65226eb3d4141616a063cdb9b9213ebd25dd36b12085dcf2b7320fb7021100000021f3337800000000000000000000

1 output(s) for total of 1937.98 upx

stealth address amount amount idx
00: 8d5c91890e570cf2cce210ee46c7b781df90323b86e6f74c2299eab224a0aa9c 1937.98 2772507 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": 526154, "vin": [ { "gen": { "height": 526094 } } ], "vout": [ { "amount": 193798, "target": { "key": "8d5c91890e570cf2cce210ee46c7b781df90323b86e6f74c2299eab224a0aa9c" } } ], "extra": [ 1, 140, 21, 171, 110, 101, 34, 110, 179, 212, 20, 22, 22, 160, 99, 205, 185, 185, 33, 62, 189, 37, 221, 54, 177, 32, 133, 220, 242, 183, 50, 15, 183, 2, 17, 0, 0, 0, 33, 243, 51, 120, 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