Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 9a875c9d9d50bb849b1175c7aba00c80f554d476e90ec020ca98708001db8b72 Tx public key: 6590a60fd73f3b92352b8aea9d92462621f24b7fb9072051ad06c0eb90999fd2 Payment id (encrypted): f319e8667071bf19
Timestamp: 1637837932 Timestamp [UCT]: 2021-11-25 10:58:52 Age [y:d:h:m:s]: 00:009:06:58:31
Block: 839366 Fee (per_kB): 0.08 (0.04) Tx size: 1.8350 kB
Tx version: 2 No of confirmations: 6690 RingCT/type: yes/3
Extra: 016590a60fd73f3b92352b8aea9d92462621f24b7fb9072051ad06c0eb90999fd2020901f319e8667071bf19

2 output(s) for total of ? upx

stealth address amount amount idx
00: 4a5406f79f188a5ebb53a23a38ff975fc281945fc3d52222726e09ad14867bfb ? 4113842 of 4136461
01: 488377aa08019361af8d83aa1ef8da92d326495966d63c7c16056337d81a79e3 ? 4113843 of 4136461

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: