Blockscout

• Name: Blockscout
• URL: https://www.blockscout.com/
• Category: open-source multichain block-explorer stack / self-hostable explorer infrastructure / contract-verification and chain-data project
• Tags: ethereum-ecosystem
• Summary: Blockscout is best kept as the project-layer note for the open-source explorer stack itself: indexer, UI, contract verification, decoded views, APIs, and microservices that chains can self-host or fork. The important taxonomy split is that this note should stay about the reusable explorer software, while blockscout captures the separate company boundary around hosted cloud deployment, SLA-backed EaaS, PRO API tiers, Chainscout metadata, and support workflow.
• What it does:
  • Provides an open-source blockchain explorer stack for inspecting blocks, transactions, addresses, tokens, NFTs, contracts, and chain statistics across many EVM networks
  • Supports smart-contract verification plus direct contract read/write interaction from the explorer UI
  • Exposes REST, GraphQL, JSON-RPC, and microservice APIs for downstream integrations
  • Can be deployed by third parties through Docker, Kubernetes, manual deployment, and other self-hosted paths
  • Uses a modular architecture with Rust microservices and adjacent tooling, making it more like an explorer platform than a single monolith
  • Ships AI-facing interfaces such as an MCP server, but the important project-level point is that these capabilities sit on top of the reusable explorer and API stack
• Key claims:
  • Official docs describe Blockscout as a full-featured, open-source blockchain explorer and emphasize that the code is community driven and available for anyone to use, explore, and improve
  • The feature docs show Blockscout as more than passive browsing: users can verify contracts, read and write to contracts, make API calls, use decoded views, and customize watchlists and account-level views
  • The running docs say Blockscout open-source software can be forked and used by any project to quickly set up a full-featured explorer environment, which is the clearest project-layer reason to keep this note separate from the company note
  • Those same docs point to Docker, Kubernetes, and manual deployment paths, plus environment variables, configs, and architecture docs, confirming that self-hostability is a first-class property of the stack
  • The running docs also point to Rust microservices in the blockscout-rs repository, reinforcing that Blockscout is an extensible explorer platform rather than one flat web app
  • The MCP docs and integration docs show the explorer project now exposing AI-facing and developer-facing interfaces on top of its underlying explorer data model, including contract metadata, balances, tokens, and chain lists
• Whitepaper: No classic whitepaper or litepaper is the point here. The strongest project-layer materials are the features docs, running docs, integrations docs, MCP docs, and the GitHub repositories already captured in ../whitepapers/blockscout-primary-sources-2026-04-25.md.
• Sources:
  • https://www.blockscout.com/
  • https://docs.blockscout.com/about/features
  • https://docs.blockscout.com/get-started/running-blockscout
  • https://docs.blockscout.com/get-started/integrating-data
  • https://docs.blockscout.com/devs/mcp-server
  • https://github.com/blockscout

Internal linkages

• Company / hosted-operations layer: blockscout.
• Best comparison points: bitquery and the-graph.
• Public-query contrast at the operator layer: dune.

Protocol / company boundary

• Keep this note on the reusable explorer stack: indexer and UI behavior, contract verification, decoded views, APIs, Rust microservices, and the deployment architecture chains can self-host or fork.
• Use blockscout for the named-operator layer around Autoscout, SLA-backed Explorer-as-a-Service, PRO API credentials, Chainscout metadata publication, hosted update cadence, and support workflow.
• That split matters because what can the Blockscout software stack do if I run it myself? and which company operates the easiest hosted explorer, metadata, and developer-access shell? are related but not identical questions.

Control surface

• At the project layer, the main leverage sits in software release cadence, which APIs and decoded views the explorer exposes, how contract verification and microservices are packaged, and what chain-specific deployment assumptions the codebase normalizes.

• The important nearby taxonomy rule is not to flatten that reusable software surface into the hosted company layer. Self-hosted Blockscout and Blockscout-managed explorer infrastructure are related, but they answer different control-surface questions.

• Read this note when the question is what does the explorer stack itself make possible? Read blockscout when the question is who operates the hosted explorer, metadata, API, and support shell many chains may treat as canonical?

• Last reviewed: 2026-08-13 UTC