Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 545f86c1a9d7d47677f8a99281cddfaa9e00f08af157eb7f36cace98fcac6b6d Tx public key: 3fc34036b4e1e10943f03e9a74ccc9eb52b87e62b3e4ba6ccf1b31cfc5f540f4
Timestamp: 1623361645 Timestamp [UCT]: 2021-06-10 21:47:25 Age [y:d:h:m:s]: 00:008:18:40:00
Block: 718722 Fee (per_kB): 0.08 (0.04) Tx size: 1.8252 kB
Tx version: 2 No of confirmations: 6329 RingCT/type: yes/3
Extra: 013fc34036b4e1e10943f03e9a74ccc9eb52b87e62b3e4ba6ccf1b31cfc5f540f4

2 output(s) for total of ? upx

stealth address amount amount idx
00: 16ba139a30bdafe1d86fe67e262a6dfdf1ce5426dbfe98d967df3be05e80a482 ? 3613537 of 3646214
01: e242b7e17776d2c30f02ca1fe5e1e68c30f87a2c4fb6cb08cdbb93fd2e503f3e ? 3613538 of 3646214

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: