Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 97c02249f767e7619eb4a87b4932b719eb51b361dcdb857ef83e8cf2ae30b946 Tx public key: c4e0d9cedc377d181b0ea13a74a2d92f0b9592f1f0c042f753d94331d7207926
Timestamp: 1685082081 Timestamp [UCT]: 2023-05-26 06:21:21 Age [y:d:h:m:s]: 00:010:06:24:02
Block: 1232855 Fee (per_kB): 0.08 (0.04) Tx size: 1.8232 kB
Tx version: 2 No of confirmations: 7378 RingCT/type: yes/3
Extra: 01c4e0d9cedc377d181b0ea13a74a2d92f0b9592f1f0c042f753d94331d7207926

2 output(s) for total of ? upx

stealth address amount amount idx
00: 26b6a8281cbd2859c481948386911b79ea768d31b121b72aea245814fff04f5c ? 5527271 of 5548284
01: d2dc576cab60204d19f1b4de6de654b86859c0efa7722da76919b0aa33c445fe ? 5527272 of 5548284

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




source code | explorer version (api): master-2019-01-05-0432f03 (1.1) | uPlexa version: 0.2.2.0-45887ac92