Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 49a91e915b76ff145b2524dce2d4550ba15eb47047c936fe90b828556d20ae5a Tx public key: 347e04e881ea0b4eceddb2bbb13663ac9bb0758afcd3b327bc6e4f4d670f60b0 Payment id (encrypted): cfa829444c1a545c
Timestamp: 1634175465 Timestamp [UCT]: 2021-10-14 01:37:45 Age [y:d:h:m:s]: 00:009:15:40:58
Block: 808817 Fee (per_kB): 0.08 (0.04) Tx size: 1.8359 kB
Tx version: 2 No of confirmations: 6966 RingCT/type: yes/3
Extra: 01347e04e881ea0b4eceddb2bbb13663ac9bb0758afcd3b327bc6e4f4d670f60b0020901cfa829444c1a545c

2 output(s) for total of ? upx

stealth address amount amount idx
00: fee04afc86e040d1688b38fb805f66be8d295a1e761e021ec7a123e253d44a0e ? 3995978 of 4025254
01: 29a85a35dd3a8125e6312674d1dc40a7f31d0565e95cd5794b42d74b7db799ad ? 3995979 of 4025254

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: