Practical overview
When it fits
Use it to browse Aleo data or as the basis for a self-hosted explorer or separate frontend. Its peer-fetching node does not validate blocks.
Who it is for
- People who want to browse Aleo blockchain data and history.
- Operators building or running a self-hosted Aleo explorer service.
- Developers connecting a separate frontend to the explorer's web API.
Documented uses
- Browse Aleo chain data and history through an explorer interface.
- Fetch Aleo blockchain data from a peer for an explorer backend.
- Store explorer data in PostgreSQL on the mainnet-newdb branch.
- Provide explorer data to a separate frontend through the web API.
Requirements & limits
The repository is public and describes the project as open source under AGPL-3.0-or-later. The README links an instance at aleoscan.io.
- The mainnet-newdb branch uses PostgreSQL for all data storage and removes the Redis requirement.
- The node fetches data from a peer but does not validate blocks; the README says to connect only to trusted peers.
- Required software includes Python 3.10 or Python 3.11.4 or later, PostgreSQL 14 or later, Rust 1.81 or later, and aleo-explorer-rust.
- Switching from the mainnet branch to mainnet-newdb requires syncing from scratch.
- The current repository frontend is planned for deprecation; the README describes a separate frontend using the web API.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up Aleo Explorer from source
Prepare and launch the explorer using the mainnet-newdb branch instructions.
Before you start
- Python 3.10 or Python 3.11.4 or later (Python 3.11.0–3.11.3 is unsupported).
- PostgreSQL 14 or later.
- Rust 1.81 or later.
- The aleo-explorer-rust dependency.
- Access to a trusted peer; the explorer node fetches blockchain data but does not validate blocks.
Steps
Import the database schema from
pg_dump.sql.Configure the application using
.env, referring to.env.example.Install dependencies with the command below; this installs
aleo-explorer-rust, while the Rust toolchain is still required. Alternatively, installrequirements.txtandaleo-explorer-rustmanually.uv syncStart the application with the command below, or use
PYTHONPATH=src python -m mainif it is not installed.uv run python -m main
Expected outcome
The explorer application is started with PostgreSQL-backed data storage; this branch stores almost full data history in the database and does not require Redis.
Guide limitations
- The node does not validate blocks; connect only to peers you trust.
- Switching from the
mainnetbranch requires a full resync. - The optional WASM compilation/install step for the old frontend is marked as not working in the README.
Compare options for Blockchain exploration
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Aleo Explorer | Browse Aleo chain data and history through an explorer interface. | Docker, Self-hosted, Server, Web | The repository is public and describes the project as open source under AGPL-3.0-or-later. The README links an instance at aleoscan.io. |
| Chainlens | Explore a supported blockchain network through a dashboard. | Docker, Self-hosted, Server | The free edition is described as free for non-commercial use and evaluation. Its deployment configuration supports Docker Compose or Kubernetes. Web3 Labs separately describes hosted plans; commercial-use inquiries are directed to the provider. |
| Ethvm | Explore Ethereum blockchain data through a client-side block explorer. | Self-hosted, Server, Web |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 11 October 2026
- Original website title
- HarukaMa/aleo-explorer · Official homepage title · retained in its source language

