Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 350b215b2b025ab1bd03d3c2cc61517bfa3791403a3fdb65285148388b6b951e Tx public key: c3fdcc5775828c1de9666e9965e44faf4cae875cb2af249b973160232d110f34 Payment id (encrypted): b330ab47f3fa73ce
Timestamp: 1546461100 Timestamp [UCT]: 2019-01-02 20:31:40 Age [y:d:h:m:s]: 04:338:01:36:21
Block: 77863 Fee (per_kB): 26.77 (14.55) Tx size: 1.8398 kB
Tx version: 2 No of confirmations: 1294294 RingCT/type: yes/3
Extra: 020901b330ab47f3fa73ce01c3fdcc5775828c1de9666e9965e44faf4cae875cb2af249b973160232d110f34

2 output(s) for total of ? upx

stealth address amount amount idx
00: 42f6f7184307aed9ec9f4811a18674e3709aedfaf394ca04a237f9ee8fac1e7e ? 203637 of 5953847
01: 116cc20edaaf676a050530afddfab95d79f27496bbf5c737f3ab92263fc4d42e ? 203638 of 5953847

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: