Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: eac7f0540d79302d96f676b98c1191a7c5a7ba1be6619462e2603ab3824b247a Tx public key: d92e80f3ac7d65f199f791b1f854b01412c183034126182383b0ad45f85b7b11 Payment id (encrypted): ade00e6eee6f3ea6
Timestamp: 1546465209 Timestamp [UCT]: 2019-01-02 21:40:09 Age [y:d:h:m:s]: 04:337:23:56:25
Block: 77892 Fee (per_kB): 12.60 (0.96) Tx size: 13.1445 kB
Tx version: 2 No of confirmations: 1294245 RingCT/type: yes/3
Extra: 020901ade00e6eee6f3ea601d92e80f3ac7d65f199f791b1f854b01412c183034126182383b0ad45f85b7b11

2 output(s) for total of ? upx

stealth address amount amount idx
00: c1c995dc9ae4ecd06b3e783f27950d18beab5c4505f251192d786ed8a799bbb6 ? 203888 of 5953795
01: c87d0e8ee87c1477de29ad7f9af10ecacefb0e4899328cd1db09d92e926bb96c ? 203889 of 5953795

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: