Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: b28af1b1905c523abf0ec6314e4e2bded6d15087f669538935d7fddb69774e3f Tx public key: 99b872d5f78d5ca17bf4734b3441d7fe5f0c8cdec76a3d8718d3aff19e883555 Payment id (encrypted): afe877eee073e9db
Timestamp: 1695143510 Timestamp [UCT]: 2023-09-19 17:11:50 Age [y:d:h:m:s]: 00:014:15:48:44
Block: 1316600 Fee (per_kB): 0.08 (0.04) Tx size: 1.8359 kB
Tx version: 2 No of confirmations: 10567 RingCT/type: yes/3
Extra: 0199b872d5f78d5ca17bf4734b3441d7fe5f0c8cdec76a3d8718d3aff19e883555020901afe877eee073e9db

2 output(s) for total of ? upx

stealth address amount amount idx
00: f0035c49cb2aa99fb4e56a2f72538bbca7ba172b88a03ab04d9551991e991663 ? 5768656 of 5802039
01: 4d024a3bbb4f147fd1a80e3b3ab4b8de0f02d33eca57437e0799cd48610ff1e2 ? 5768657 of 5802039

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: