uPlexa Block Explorer

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

Tx hash: 2bdf7b90dd47977f9152b010e83f31a3bc9a4a3eb7cf5ff2cdcd0d28a9a69121

Tx prefix hash: 690dbccdd54fccbf6284bf9456771754fd014de9bad272f11e6ecd9b34309e1e
Tx public key: 0baff610e5c3b128ee585319b5970e66ea9e959f20cf33cd8b329e2dbde99d3f
Timestamp: 1581670074 Timestamp [UCT]: 2020-02-14 08:47:54 Age [y:d:h:m:s]: 00:055:02:54:20
Block: 371247 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 39677 RingCT/type: yes/0
Extra: 010baff610e5c3b128ee585319b5970e66ea9e959f20cf33cd8b329e2dbde99d3f021100000066cefaba00000000000000000000

1 output(s) for total of 2010.86 upx

stealth address amount amount idx
00: 37cef0a55b59cb63168d013d1f2ebcba8071afb691557e8b3112fb0d6b1878b0 2010.86 2092543 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": 371307, "vin": [ { "gen": { "height": 371247 } } ], "vout": [ { "amount": 201086, "target": { "key": "37cef0a55b59cb63168d013d1f2ebcba8071afb691557e8b3112fb0d6b1878b0" } } ], "extra": [ 1, 11, 175, 246, 16, 229, 195, 177, 40, 238, 88, 83, 25, 181, 151, 14, 102, 234, 158, 149, 159, 32, 207, 51, 205, 139, 50, 158, 45, 189, 233, 157, 63, 2, 17, 0, 0, 0, 102, 206, 250, 186, 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