Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: fee376a818c77c85094a8e67965ba7c4a22a0314c971af2beaaa484b3fc9f38a Tx public key: 053bfbb42bffe8674ac87d784a611b64f41760794aa22be19ed03821122267df Payment id (encrypted): 4a692e14b751ccfb
Timestamp: 1626929241 Timestamp [UCT]: 2021-07-22 04:47:21 Age [y:d:h:m:s]: 00:010:23:16:04
Block: 748476 Fee (per_kB): 0.08 (0.04) Tx size: 1.8369 kB
Tx version: 2 No of confirmations: 7893 RingCT/type: yes/3
Extra: 01053bfbb42bffe8674ac87d784a611b64f41760794aa22be19ed03821122267df0209014a692e14b751ccfb

2 output(s) for total of ? upx

stealth address amount amount idx
00: a888f38b4294544539b3a2a62ea6e9520ffb96e1e715745bb0785f0ee4f423e6 ? 3760745 of 3794381
01: 6132b63f6fe36d08e7abae772be89aeef9293f5b79dfe60fd2222e60cf620498 ? 3760746 of 3794381

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: