Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: b996cd08cd2779fc62998f68186bd75022dc46a57473fe8ec6b873931e8f8d05 Tx public key: 7adf91951088c17d7a3ab0822248611551e38c23b2bd481d71ced73c0730e34d Payment id (encrypted): 9b366f9349903489
Timestamp: 1659747112 Timestamp [UCT]: 2022-08-06 00:51:52 Age [y:d:h:m:s]: 00:012:09:11:31
Block: 1021871 Fee (per_kB): 0.56 (0.04) Tx size: 13.1660 kB
Tx version: 2 No of confirmations: 8916 RingCT/type: yes/3
Extra: 0209019b366f9349903489017adf91951088c17d7a3ab0822248611551e38c23b2bd481d71ced73c0730e34d

2 output(s) for total of ? upx

stealth address amount amount idx
00: e9d5267be1fde9b2ab7bd65d840025d28bbe98c6008ff2fcf8e2cef8a8ac08ae ? 4854878 of 4890197
01: dc4d5ae4f7299aca0f981459331c3bcbc28e931a8a6f952538d77e623c3e6c89 ? 4854879 of 4890197

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: