Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: f0ad2050de7342a984bb9b9f5f8830da4e96b6e26ac6ffff406b8c3033c80717 Tx public key: c894bc21f73385f3e0a6d3e3d7d0de112aca67f9d1c797868f56b6c3da7cb8f8
Timestamp: 1620124861 Timestamp [UCT]: 2021-05-04 10:41:01 Age [y:d:h:m:s]: 00:006:13:55:27
Block: 691753 Fee (per_kB): 0.12 (0.05) Tx size: 2.6367 kB
Tx version: 2 No of confirmations: 4747 RingCT/type: yes/3
Extra: 01c894bc21f73385f3e0a6d3e3d7d0de112aca67f9d1c797868f56b6c3da7cb8f8

2 output(s) for total of ? upx

stealth address amount amount idx
00: 4fa35ce57f54194d93b6941d5f8e73c234d1c642aea95678221a4792e40f5443 ? 3461211 of 3489632
01: 255128f4f725ab3ba1b2bb51fe455c5a6fedbc7a4f131f3c58a7173a1693bb0e ? 3461212 of 3489632

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