Start and use an instance of the LEZ Explorer
Get a clear view of on-chain activity including blocks, transactions, and accounts.
The LEZ Explorer lets you inspect the state of the Logos Execution Zone in real time. This procedure walks you through starting all required services locally and using the Explorer UI to browse blocks, search transactions, and look up account balances. It is intended for developers working on testnet v0.2 who want to verify on-chain state or test wallet interactions.
If you don't want to run your own LEZ explorer instance, navigate to the public LEZ explorer.
Before you start, make sure you have the following:
- Linux or macOS operating system
- Docker, Rust toolchain, and
cargoinstalled cargo-leptosinstalledjustinstalled- A local clone of the LEZ repository
- A running instance of an LEZ Indexer
What to expect
- You can browse all committed blocks and click through to inspect individual block details.
- You can search for transactions and accounts and view their current state and balances.
Start the LEZ Explorer
-
Navigate to your local clone of the LEZ repository.
-
In a new terminal window, start the LEZ Explorer:
just run-explorerinfoBy default, the LEZ Explorer connects to the LEZ Indexer at
http://localhost:8779. Set theINDEXER_RPC_URLenvironment variable or pass--indexer-rpc-urlto use a different address. -
Open
http://localhost:3000/in your browser.You will see a No blocks found message initially:

After approximately one minute, refresh the page. Blocks will appear:

Browse blocks, transactions, and accounts
-
Click any block in the list to view its details.

-
Use the search bar to look up a block, transaction, or account by ID.


Troubleshooting LEZ Explorer
Why does the Explorer show "No blocks found" after startup?
Block production takes up to one minute after the stack starts. Refresh the page manually; live updates are not yet implemented.
Why does LEZ Explorer fail to load block data?
Confirm that the LEZ Indexer is running and reachable. By default, the Explorer connects to http://localhost:8779. Check that just run-indexer is active in its terminal and that no firewall rule is blocking port 8779.