Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 07eaab3283935594a7bb392af5dd7c2a3eb79b6948280d267f5843e5fd02b28e Tx public key: 0850f06f235cd2dd82dc9a28eef18c76b314135df97ae073a0c68cfedd036c2c Payment id (encrypted): b4e70cfd8bbaa42f
Timestamp: 1623363181 Timestamp [UCT]: 2021-06-10 22:13:01 Age [y:d:h:m:s]: 00:008:18:11:26
Block: 718729 Fee (per_kB): 0.44 (0.04) Tx size: 10.7363 kB
Tx version: 2 No of confirmations: 6319 RingCT/type: yes/3
Extra: 010850f06f235cd2dd82dc9a28eef18c76b314135df97ae073a0c68cfedd036c2c020901b4e70cfd8bbaa42f

2 output(s) for total of ? upx

stealth address amount amount idx
00: 4ccd15df3f1fc8d983286d429834c6fd89fc2f702a11b238aca82765ea5e78d2 ? 3613596 of 3646198
01: dbeb1488b77dc1d08905535f3f8d31de5340b642ec2905365238a46dcc816abd ? 3613597 of 3646198

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: 0.2.2.0-45887ac92