Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 9ec343e54dfa7c519ed1c104d06f7bc5151c7832cc54506f0b3348717ba75f2c Tx public key: 07ca6550e54d649f202e2f3582d459a8f5db663bb29079aca0dbbe1d21d4287b Payment id (encrypted): 6805831366d91c65
Timestamp: 1655980416 Timestamp [UCT]: 2022-06-23 10:33:36 Age [y:d:h:m:s]: 00:010:13:23:48
Block: 990518 Fee (per_kB): 0.08 (0.04) Tx size: 1.8379 kB
Tx version: 2 No of confirmations: 7608 RingCT/type: yes/3
Extra: 0107ca6550e54d649f202e2f3582d459a8f5db663bb29079aca0dbbe1d21d4287b0209016805831366d91c65

2 output(s) for total of ? upx

stealth address amount amount idx
00: 93d736151cb1abe04ea3fa5d3d380a40eb836469abdbe147387a455bd58856b9 ? 4717425 of 4753470
01: fb4cdd9899ed2dc301235bfca3e231d011cc6543c6c41e4db792b25fae7210a1 ? 4717426 of 4753470

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: