Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: f8fb3395d1b6c3e249bb47219321b1fc5bd2ddcd4ff0a0457917f527cea375c9 Tx public key: 52bee09a2d5ebb1245069b2ec547e30d172ed82043c54de73f7b16e4ffdfaf2c Payment id (encrypted): 957f1fe4a57b55f4
Timestamp: 1626929241 Timestamp [UCT]: 2021-07-22 04:47:21 Age [y:d:h:m:s]: 00:010:22:22:05
Block: 748476 Fee (per_kB): 0.08 (0.04) Tx size: 1.8398 kB
Tx version: 2 No of confirmations: 7863 RingCT/type: yes/3
Extra: 0152bee09a2d5ebb1245069b2ec547e30d172ed82043c54de73f7b16e4ffdfaf2c020901957f1fe4a57b55f4

2 output(s) for total of ? upx

stealth address amount amount idx
00: e4982897e6aa0aeb68b863126407f3b72b59149108408d790afb3bc692f30d12 ? 3760747 of 3794230
01: d0aa7c08247912f4d433c7630f62472b367ba178d4f17aef520d33fc1e7eccb8 ? 3760748 of 3794230

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: