Blockscout Explained: Blockchain Search, Verification, Hosting and Licensing

Blockscout is software and infrastructure for exploring blockchain activity, especially on networks compatible with the Ethereum Virtual Machine. It turns blocks, transactions, addresses, tokens and contract information into searchable pages and developer-accessible data. It does not become the blockchain merely because users rely on its interface to understand a transaction.

There is also a current licensing distinction. Blockscout's April 23, 2026, release notes state that version 11 moved from GPL-3.0 to a source-available license with conditions affecting commercial resale. Describing all current releases simply as unrestricted open-source software would miss that change.

Who runs Blockscout, and what an explorer does

The project is maintained by the Blockscout team, and its official materials identify Blockscout Limited. Its software can support explorers operated for different chains, while the company also offers hosted services and developer products. The branding on an explorer does not necessarily identify the same operational arrangement in every deployment.

The official Blockscout site provides access to the product ecosystem. A typical explorer collects information from blockchain nodes, indexes it and presents it in forms useful to people and applications. That indexing layer is why a transaction can exist on-chain before every interface has fully displayed it.

An explorer is not normally a custodian holding the assets shown on its pages. Looking up an address does not transfer control of it to the website. The wallet guide explains why viewing a balance and possessing the keys able to spend it are separate capabilities.

How to read a transaction without overinterpreting it

Start with the correct network and transaction identifier. On a transaction page, useful fields include status, the block containing it, the sender, the destination, fees and token-transfer information. A contract interaction may contain several effects rather than one simple payment.

A successful transaction status means the network processed the transaction under its execution rules. It does not automatically mean a customer received the expected economic outcome. A token approval can succeed without transferring the asset, while an exchange may not yet have credited an on-chain deposit.

Token names and symbols also need caution. Different contracts can adopt similar labels, and unsolicited tokens can appear in an address's history. The contract address and recognized issuer matter more than a familiar-looking ticker in a list.

For unfamiliar fee fields, the transaction-fee guide separates the resource charge from the value transferred and from a service's additional charges. An explorer can show the on-chain component without knowing every commercial agreement surrounding it.

Verified contract code is not a security audit

Contract verification allows source code and compilation information to be matched to deployed bytecode. Blockscout supports verification workflows for developers and exposes verified information to users. This makes a contract easier to inspect than an unexplained block of machine-level instructions.

The match answers a limited question: whether the provided source corresponds to the deployed program under the relevant verification process. It does not establish that the program is well designed, economically sound or free of exploitable behavior.

Proxy contracts create another distinction. A proxy can route execution to an implementation that may change under administrative controls. A reader must understand the actual implementation and upgrade permissions rather than treating a verified proxy as the final word on future behavior.

Reading contract information is also different from using a write function. A write operation can require a wallet signature, spend gas or authorize changes. An explorer's interface does not make an unfamiliar transaction harmless.

Public pages, APIs and managed hosting serve different users

Public explorer pages are designed for people checking activity. Developers can use APIs to retrieve information programmatically. Blockscout's March 2026 PRO API announcement describes a shared account for accessing multichain on-chain data, rather than forcing every application to use a separate interface for every chain.

Autoscout addresses another need: deploying and operating an explorer for a network. Its published workflow includes deployment status, logs and configuration options. A chain team choosing managed hosting is buying operational help, not merely permission to look up a transaction.

These products should be compared against the task. A person inspecting a single payment does not need the same service as a developer maintaining a portfolio application or an operator indexing a new chain.

What is free, and where costs appear

As checked on October 16, 2026, ordinary public browsing does not require a paid explorer subscription. Self-hosting still creates infrastructure costs, including blockchain access, servers, storage, monitoring and engineering time. A software download being available without a charge does not make those resources free.

Managed hosting and commercial API use have their own plans and limits. A universal current price for every hosted deployment could not be established from the accessible public material reviewed for this explainer. Teams should confirm the current quote, included capacity and overage terms for their actual chain and workload.

Do not compare an old promotional hosting figure with a current production quote as though both cover the same service. Historical data volume, indexing requirements, additional features and support expectations can materially change the operational scope.

The 2026 license change matters most to resellers

Blockscout's version 11 announcement says standalone projects and chains can continue to download, run and modify the software without a charge. It describes a commercial-license requirement for providers reselling Blockscout-powered services and a visible attribution requirement for interfaces built on it.

The important distinction is between source availability and a license permitting every commercial use without additional conditions. A team offering hosted explorers to paying customers should examine the license for the particular version and components it deploys, not rely on a historical GPL description.

This is a practical procurement issue rather than a reason to assume the explorer has stopped functioning. Technical capability, hosting cost and permission to resell are three separate questions. Each needs its own answer.

Privacy, availability and interpretation remain limits

A public blockchain can make transaction records visible while the explorer operator can still observe ordinary website or API access information. Users should consider the privacy implications of repeatedly searching their own addresses through a hosted service. A pseudonymous address is not the same thing as an anonymous browsing session.

Indexing delays, outages and configuration differences can also affect what an explorer displays. For a consequential discrepancy, compare the network, block height and transaction identifier before concluding that funds have disappeared. Another independent view can help distinguish a display problem from an on-chain event.

Blockscout is useful when it makes evidence easier to inspect without being mistaken for the authority behind every claim attached to that evidence. Its contract tools, APIs and hosting products extend that role, but none replaces understanding the underlying application, asset or network.