Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 0a230245ac0753be782c522d84d0796fde3471be779234d07b7b252df924a48b Tx public key: 3e64cf32da3773d6ab5a11631d214fa2ea72a3168e7dbf80e436c4ce92402fa4 Payment id (encrypted): c34dee6e3ef30f48
Timestamp: 1620126338 Timestamp [UCT]: 2021-05-04 11:05:38 Age [y:d:h:m:s]: 00:006:13:45:50
Block: 691762 Fee (per_kB): 0.08 (0.04) Tx size: 1.8379 kB
Tx version: 2 No of confirmations: 4745 RingCT/type: yes/3
Extra: 013e64cf32da3773d6ab5a11631d214fa2ea72a3168e7dbf80e436c4ce92402fa4020901c34dee6e3ef30f48

2 output(s) for total of ? upx

stealth address amount amount idx
00: c679e11ca892517294caa72f8cd4c86a2781c7e696a408e0e7f46893b6828b52 ? 3461269 of 3489662
01: 17ed1e0fd3955ed6d38f3d39aac38d29c35705b44903b7b4fe9aa8a15e822f07 ? 3461270 of 3489662

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: