Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 01d92575c364afe0baa1a9634a4ab1a457f6873f29ac9753258a5f5f423814ad Tx public key: 42df158b56e9121174387bc371692a41276c764fe84456d7fb0891cf733ffd14 Payment id (encrypted): ebec7d8e9f4af77f
Timestamp: 1623362451 Timestamp [UCT]: 2021-06-10 22:00:51 Age [y:d:h:m:s]: 00:008:18:05:37
Block: 718725 Fee (per_kB): 0.08 (0.04) Tx size: 1.8408 kB
Tx version: 2 No of confirmations: 6316 RingCT/type: yes/3
Extra: 0142df158b56e9121174387bc371692a41276c764fe84456d7fb0891cf733ffd14020901ebec7d8e9f4af77f

2 output(s) for total of ? upx

stealth address amount amount idx
00: 9034a395f1b2106c7143afaefaacc7c31bf7525359b384d8a6c9c59d6bfde363 ? 3613572 of 3646142
01: b2f5d730b205d3aa88d6d1aefb7f0e183f63fa0702f8b572e18525d23bb0b312 ? 3613573 of 3646142

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: