Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 0d144b6dfe35bf2ef56d8812dc359b0c89472cb3a3a5bada560623c002fb7bd9 Tx public key: d9b26745743c6c919313978be74054e8695ec43ea602a1dd30c5430595a02f7f Payment id (encrypted): 18a7c87f18b7d5ee
Timestamp: 1642189501 Timestamp [UCT]: 2022-01-14 19:45:01 Age [y:d:h:m:s]: 00:014:00:15:37
Block: 875596 Fee (per_kB): 0.08 (0.04) Tx size: 1.8379 kB
Tx version: 2 No of confirmations: 10093 RingCT/type: yes/3
Extra: 01d9b26745743c6c919313978be74054e8695ec43ea602a1dd30c5430595a02f7f02090118a7c87f18b7d5ee

2 output(s) for total of ? upx

stealth address amount amount idx
00: 263da80ebb27588092f93728cb6930c73c8335be3167f7b3b81f77867e9b9334 ? 4243787 of 4286780
01: b6b728a2965cd2b2a8c440f3c538873ae9a9f6f2516daf75ece0ad9b2655f285 ? 4243788 of 4286780

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: