Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 14e42fb9f3fde2d9830708caa260a0d8ec143078603352301d346398598540c2 Tx public key: 3ad8779fb323a3ab0af5dac0c39aed3ad55e93bd3026ce924c5998a6df76f23a Payment id (encrypted): d8bc8285f929688f
Timestamp: 1617913606 Timestamp [UCT]: 2021-04-08 20:26:46 Age [y:d:h:m:s]: 00:005:03:09:38
Block: 673298 Fee (per_kB): 0.81 (0.10) Tx size: 8.3174 kB
Tx version: 2 No of confirmations: 3683 RingCT/type: yes/3
Extra: 013ad8779fb323a3ab0af5dac0c39aed3ad55e93bd3026ce924c5998a6df76f23a020901d8bc8285f929688f

2 output(s) for total of ? upx

stealth address amount amount idx
00: bf6656ae68fd5b96818c171f9101c04128519aa6baa52d395e05da2ea616ffea ? 3352763 of 3370881
01: 4146727b8441036fffa78c936bf1d19943cfa0d7c36ac40e3ac03a253d85d84b ? 3352764 of 3370881

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: