Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 146bf0028f1f04a73007b1c23001d3abc833f79c8ea206c5cce79f92685fcb3c Tx public key: 897ba9fed88dc58c3116fc5dce820b908e46c8e14a557a96a69701a8d466e6a0 Payment id (encrypted): 9f495b2375c0848c
Timestamp: 1655981115 Timestamp [UCT]: 2022-06-23 10:45:15 Age [y:d:h:m:s]: 00:010:13:54:09
Block: 990523 Fee (per_kB): 0.08 (0.04) Tx size: 1.8369 kB
Tx version: 2 No of confirmations: 7632 RingCT/type: yes/3
Extra: 01897ba9fed88dc58c3116fc5dce820b908e46c8e14a557a96a69701a8d466e6a00209019f495b2375c0848c

2 output(s) for total of ? upx

stealth address amount amount idx
00: 2aa9602997e800ef41327c5afbe36a4e54ba48e818e335ba2cbe63079964695a ? 4717451 of 4753624
01: 35f4320fab635d051b06eb2420c3d0020c296c8234a6d047ff6b1edb548fb546 ? 4717452 of 4753624

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: