Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 9964895667ec4f2f75b18db598b5a4b1f322e508aaf955ee5ed47c336538e485 Tx public key: 4143a93996bc1ce0aff090cd2f2811c9c49dc72adfe6133f47beb379fa817bb5 Payment id (encrypted): 0ae6b64c429241ff
Timestamp: 1620124668 Timestamp [UCT]: 2021-05-04 10:37:48 Age [y:d:h:m:s]: 00:006:13:49:40
Block: 691750 Fee (per_kB): 1.26 (0.10) Tx size: 13.1904 kB
Tx version: 2 No of confirmations: 4746 RingCT/type: yes/3
Extra: 014143a93996bc1ce0aff090cd2f2811c9c49dc72adfe6133f47beb379fa817bb50209010ae6b64c429241ff

2 output(s) for total of ? upx

stealth address amount amount idx
00: 68175b8cd8d473a48861789726b2591a3d6e0ffa7f65b821c41be3f42e9ad7de ? 3461176 of 3489604
01: 26231144cda200d388ca47fec9dc50fe71f3018df250ef2182c53ca409370df5 ? 3461177 of 3489604

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: