About ExplorerScan

A directory of every block explorer, grouped by who runs it.

What this is

ExplorerScan indexes the block explorers themselves. Most chains have several, most of them are deployments of a handful of underlying platforms, and almost nobody keeps track of which is which. We group every explorer host under the provider that actually operates it, so one Etherscan row stands for its many chain deployments instead of thirty near-identical entries.

Each host also gets a posture reading. An explorer is where people go to verify that a transaction really happened, which makes its TLS configuration and certificate chain worth watching. Several of the incidents on our incidents page began with someone serving a convincing page from a hijacked name.

ExplorerScan is the registry. We maintain the taxonomy ourselves, we own every record, and we do not mirror other catalogues. If an explorer is not in our database it does not exist for our purposes.

How it works

We catalogue every explorer URL we can find, chain by chain, from our own canonical records.
Hosts are grouped by the provider that runs them, with multi-chain deployments rolled up under one entry.
A Rust prober measures each host’s TLS version, cipher, certificate chain and post-quantum key exchange.
Results are written to Cloudflare R2 and KV, then served from the edge.
Chain shortcuts resolve straight to a chain’s explorer view: https://<chain>.explorerscan.com.

Privacy first, by construction

We log no IP addresses and set no tracking cookies of our own. That is not a setting we can quietly flip: the IP field does not exist in the data model. Google Analytics runs on this domain and does see your IP, so we say so plainly rather than claim a clean sweep. RPCScan carries no tag at all. The privacy policy spells out exactly what is stored and by whom.

Giving back

10% of advertising revenue goes to animal welfare, calculated on gross revenue. Every donation is published with its date, its amount and the revenue it came from, so the arithmetic is auditable rather than asserted. The ledger lives at /giving and is empty today, because no advertising has been sold yet.

Who runs this

ExplorerScan is built and maintained by Stephen Molnar in Las Vegas, NV, independently and without outside funding. It is one person and a small fleet of probes, not a company, which is worth knowing when you judge how much to rely on it.

Corrections, additions and complaints all go to the same place: contact@explorerscan.com, or through the request form if you would rather it be tracked. Source and issues live at github.com/explorerscan.

Built on

Both brands are one Next-flavoured React Server Components app running on vinext, Cloudflare’s experimental Vite and RSC build tool that drops in for the Next CLI. We picked it deliberately. It gives us file-system routing, async server components and edge-friendly route handlers, while shedding Webpack’s build-time weight in favour of Rolldown and @vitejs/plugin-rsc, and vinext build is measurably faster than next build on the same source tree.

The dependency tree is small on purpose. The declared package.json has three top-level packages (react, react-dom, vinext) and the rest of the install is build tooling. No CSS framework, no UI library, no HTTP client, no router library, no ORM. Every component here is hand-rolled around fetch, <svg> and inline style objects.

The backend follows the same discipline: a hand-rolled Rust workspace (bn-tls, bn-http, bn-x509, bn-asn1, bn-h2) with a strict allow-list of audited crypto primitive crates. No tokio, no rustls, no openssl, no reqwest, no hyper. See /security for the full posture.