Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: db2cf7fbf81ae7980fb093374b42d07fff5a2df5710e3181b6e2d9b90543b19e Tx public key: d1789fa8feb8d8563869274a431982cfd3ff4e578bb1ce08f59d63998f65d522 Payment id (encrypted): c461556f821777d5
Timestamp: 1546464989 Timestamp [UCT]: 2019-01-02 21:36:29 Age [y:d:h:m:s]: 04:338:00:48:05
Block: 77890 Fee (per_kB): 1.80 (0.98) Tx size: 1.8369 kB
Tx version: 2 No of confirmations: 1294275 RingCT/type: yes/3
Extra: 020901c461556f821777d501d1789fa8feb8d8563869274a431982cfd3ff4e578bb1ce08f59d63998f65d522

2 output(s) for total of ? upx

stealth address amount amount idx
00: 35d7a755209cfaa836564859165ed4c3fd211bbb4cd115484879a313ddd7379f ? 203854 of 5953892
01: a17bf4b77fed6b03dffe3e6e8993455b2c28df17114a73865baa345d8e0c4cad ? 203855 of 5953892

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: