Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 72375a44410abb1e916b223efa9967b5d5a4fc4a9de8cce0480e139ae2fcc7bd Tx public key: 66c70e3bbf38faa13c0f2c51707b8fe45fc6b8d8c42b345496a46805f83436bc Payment id (encrypted): dfd63550401178c9
Timestamp: 1620124827 Timestamp [UCT]: 2021-05-04 10:40:27 Age [y:d:h:m:s]: 00:006:15:23:38
Block: 691752 Fee (per_kB): 1.26 (0.10) Tx size: 13.1738 kB
Tx version: 2 No of confirmations: 4801 RingCT/type: yes/3
Extra: 0166c70e3bbf38faa13c0f2c51707b8fe45fc6b8d8c42b345496a46805f83436bc020901dfd63550401178c9

2 output(s) for total of ? upx

stealth address amount amount idx
00: 3e0285c605f4aa2b4a5ec4ac17c89343fe71d06f1c9126583f1df4ad5028ba9c ? 3461206 of 3489934
01: 39ae09d785dcb16e4693b363d76c2a7e1fc3450149361bc0e52fa905f9c5a179 ? 3461207 of 3489934

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