Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: c8d5940b317aff4d526fe3c6812f5a023da26ff20b2957450e127f2abc8e6c7b Tx public key: dfc1963d0f38733b0e6048ecf82ec3e6eb751afc8cc2dc5384cab3bf8a52ba2f Payment id (encrypted): cba11dd11b2d3364
Timestamp: 1620124668 Timestamp [UCT]: 2021-05-04 10:37:48 Age [y:d:h:m:s]: 00:006:15:23:24
Block: 691750 Fee (per_kB): 0.32 (0.17) Tx size: 1.8359 kB
Tx version: 2 No of confirmations: 4802 RingCT/type: yes/3
Extra: 01dfc1963d0f38733b0e6048ecf82ec3e6eb751afc8cc2dc5384cab3bf8a52ba2f020901cba11dd11b2d3364

2 output(s) for total of ? upx

stealth address amount amount idx
00: df22eda94a4843664a89ab081ff8dba5c4cd2a32608d45cb84b0f13e621d375a ? 3461164 of 3489931
01: 14274612890e0771382ccb1f1a6adfbfbf6facdb83ad7762202050922ca47f34 ? 3461165 of 3489931

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: