Blockscout: a self-hosted EVM block explorer you deploy yourself

What Blockscout is for, and who actually deploys it

Blockscout is a blockchain explorer for EVM chains. The README describes it as "an open-source alternative to centralized, closed source block explorers such as Etherscan, Etherchain and others", and the scope is wider than Ethereum Mainnet: it names Ethereum Classic, Optimism, Gnosis Chain, plus testnets, private networks, L2s and sidechains.

The audience follows from that. If you operate a chain that Etherscan does not index, you cannot simply point users at Etherscan. You need an explorer of your own, with your chain's genesis, your token contracts, your verified sources. Blockscout is the self-hosted option for that job. The README says it "currently supports several hundred chains and rollups", with a list at chains.blockscout.com.

The project is not a hosted service. Nothing in the README offers a managed plan or a support contract. You run it, you operate its database, and you handle its upgrades.

How Blockscout works: Elixir, Postgres and an indexer

Blockscout is written in Elixir, and the repository is an umbrella project: the top level holds a mix.exs, a mix.lock, an apps/ directory, config/, docker/, docker-compose/ and rel/. That layout is the standard shape of an Elixir/OTP release, where rel/ defines what gets packaged and apps/ holds the individual applications that make up the system.

The data flow is the usual explorer pattern. An indexer process reads blocks from your chain's JSON-RPC endpoint, writes them into a database, and the web application serves pages and API responses from that database. The README also lists verifying and interacting with smart contracts.

Two consequences fall out of this design. First, the explorer's freshness depends on the indexer keeping up with the chain head; a lagging indexer shows stale balances and missing transactions. Second, the database is not a cache you can drop. It holds indexed chain history and verification records, so it grows with your chain and needs real operational care.

Installing Blockscout and reaching a running explorer

The README does not put installation steps inline. It points at the documentation and lists deployment paths: manual deployment, Docker Compose, Kubernetes, a manual backend plus old UI variant, and Ansible. Environment variables and configuration options have their own documentation pages. Pick one path and follow it there rather than improvising.

Docker Compose is the shortest route for a first look. The repository ships a docker-compose/ directory and a docker/ directory, and the documentation has a Docker Compose deployment page. Follow that page for the exact commands.

Configuration is environment driven. The documented environment variable reference is the place to set your chain's RPC endpoint, database credentials and chain identity; the README links it as "ENV variables". Do not guess variable names, since the documentation is the authority and the names are not self-evident.

Once the instance is up, the first real use is a search. Paste a transaction hash or an address into the search box and confirm that Blockscout returns data from your chain rather than an empty page. If it returns nothing, the indexer is not reading your RPC endpoint correctly, and the environment configuration is the first thing to check.

The Etherscan-compatible API is the part integrators care about

The README itself does not describe an API, so check the project documentation at docs.blockscout.com for what an instance exposes before you plan an integration on it, and verify the specific endpoints you depend on against your own instance.

Where Blockscout is the wrong choice

The clearest case against Blockscout is when you do not run a chain. If you want to inspect Ethereum Mainnet transactions, public hosted instances already exist, and deploying your own indexer to mirror Mainnet means storing and maintaining a copy of data someone else already serves.

The second case is operational capacity. Blockscout is an Elixir application backed by a database that grows with chain history. Someone has to run it, monitor the indexer, apply upgrades and handle database growth. A team without that capacity is better served by a hosted explorer, even at the cost of control.

The third case is licence fit. The repository's licence field is NOASSERTION and the README states the project is licensed under the Blockscout Software Licence, with third-party components under their own terms. That is not a standard OSI licence such as MIT or Apache-2.0, and the README does not summarise its terms. If your organisation has a policy about which licences it accepts, read the LICENSE file before you build on it.

A fourth limitation is inherent to the design: the explorer can only show what the indexer has ingested. During a reorg, a backlog or an RPC outage on your node, the explorer lags or shows inconsistent state. That is a property of any indexed explorer, but it is worth stating plainly because users treat an explorer as ground truth.

How Blockscout differs from Etherscan and from running your own indexer

The README names Etherscan directly as the thing Blockscout is an alternative to. The difference is not features, it is control and coverage. Etherscan is a closed source, centralized service that indexes the chains its operators choose to support. Blockscout is source-available software you deploy against a chain you choose, including private networks and testnets that no commercial explorer will index.

That difference cuts both ways. You gain coverage of your own chain and control over the data. You lose the operational simplicity of a service someone else runs, and you take on the work of keeping the indexer current.

The second alternative is the do-it-yourself indexer. A team could write its own ingestion pipeline against the chain's JSON-RPC and serve its own API. The reason not to is the surface area: contract verification, accounts and balances, and interaction with smart contracts and applications. Reproducing that is months of work. Building your own only makes sense if your requirements diverge sharply from what an explorer does.

Between those two, Blockscout occupies the middle: more work than using Etherscan, far less work than writing an explorer from scratch.

Maintenance, upgrades and licence implications

The repository is not archived, and the last push was on 2026-11-02. Recent releases are frequent: v12.0.2 on 2026-10-16, v12.0.3 on 2026-10-21 and v12.0.4 on 2026-11-02. A CHANGELOG.md sits at the repository root, so release-by-release changes are documented in-tree rather than only in release notes.

That cadence has a cost. Frequent releases mean upgrade work, and an Elixir application with a database behind it usually means migrations. The repository includes a rel/ directory for release packaging and a docker-compose/ directory, so container-based upgrades are the path with the least custom tooling. The README does not document rollback, so plan your database backups before upgrading rather than after.

On licensing, the README states the project is licensed under the Blockscout Software Licence and points to the LICENSE file for full terms. It also notes that third-party components remain under their own licences, with details in dependency manifests and bundled notices. The repository's licence field reads NOASSERTION, which means GitHub could not classify it automatically. The practical implication is that you cannot assume MIT or Apache-2.0 terms apply. Whether the Blockscout Software Licence is acceptable for your use, particularly for a commercial or modified deployment, is a question for your own legal review; this article does not give legal advice and the README does not summarise the terms.

Editorial conclusion

Adopt Blockscout if you run an EVM chain, L2, sidechain or private network and need a public explorer you control. Do not adopt it if you only want to browse Ethereum Mainnet, since public hosted instances already exist, or if you need a hosted SaaS with a support contract. Before committing, verify three things: your chain's JSON-RPC endpoint answers the calls Blockscout needs, which deployment path fits your infrastructure (manual, Docker Compose, Kubernetes or Ansible), and how the Blockscout Software Licence applies to your intended use, which is a question for your own counsel rather than this article.

Frequently asked questions

Official sources

1. blockscout/blockscout on GitHub
2. Issues
3. Project website
4. README
5. Releases