Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: ccbd81b3d4a9b5dca52cfac0fc6b8b084c73e6ec2b18dff04e813c2840a37ad1 Tx public key: 99648aa28136a072c833e3c8d4f2df43f26d2175e7a8a8d880a1f5c9b2e52e0e
Timestamp: 1546460195 Timestamp [UCT]: 2019-01-02 20:16:35 Age [y:d:h:m:s]: 04:338:01:58:50
Block: 77859 Fee (per_kB): 10.80 (4.10) Tx size: 2.6357 kB
Tx version: 2 No of confirmations: 1294301 RingCT/type: yes/3
Extra: 0199648aa28136a072c833e3c8d4f2df43f26d2175e7a8a8d880a1f5c9b2e52e0e

2 output(s) for total of ? upx

stealth address amount amount idx
00: a6931a5b40cfdd450ee404d5e3c23d32d3d4e2dc93e30dedd420a365e50d33da ? 203547 of 5953858
01: b4fe43fc4260080957b787068db95a4d014739770c678beea1bc4ed2e7b4a0ac ? 203548 of 5953858

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: