uPlexa Block Explorer

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

Tx hash: 5b88cc21b41c7efcf302f2514b61e2fed0fd08d019df94636d61afba0fd5e305

Tx prefix hash: 833791703b0452fa75d5f454b961ab5d54c2b3d3bf4fa90033a3c7c81634fb89
Tx public key: bf55dae9d1b0c6bf1ef3af135b1bd5a68e754432744c831581b4fcdf0034c4c0
Timestamp: 1602972650 Timestamp [UCT]: 2020-10-17 22:10:50 Age [y:d:h:m:s]: 00:007:07:17:07
Block: 548845 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 5278 RingCT/type: yes/0
Extra: 01bf55dae9d1b0c6bf1ef3af135b1bd5a68e754432744c831581b4fcdf0034c4c002110000002aaac62300000000000000000000

1 output(s) for total of 1927.70 upx

stealth address amount amount idx
00: 3687e62f80bc81684ea800d2b2a6bec9a763f1be2ebc5e4e42bc23fc4147f80c 1927.70 2871425 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": 548905, "vin": [ { "gen": { "height": 548845 } } ], "vout": [ { "amount": 192770, "target": { "key": "3687e62f80bc81684ea800d2b2a6bec9a763f1be2ebc5e4e42bc23fc4147f80c" } } ], "extra": [ 1, 191, 85, 218, 233, 209, 176, 198, 191, 30, 243, 175, 19, 91, 27, 213, 166, 142, 117, 68, 50, 116, 76, 131, 21, 129, 180, 252, 223, 0, 52, 196, 192, 2, 17, 0, 0, 0, 42, 170, 198, 35, 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