Link to Blockscout

​

Replace the primary explorer link

In most cases simply replacing the first part of the url is all that is needed to replace Etherscan with Blockscout. For example, replace https://etherscan.io/ with https://eth.blockscout.com/ in your code and the corresponding links to blocks, transactions, etc. will be mapped to Blockscout rather than Etherscan. Blockscout linking architecture follows EIP-3091 standardization for the following routes:

• Blocks <BLOCK_EXPLORER_URL>/block/<BLOCK_HASH_OR_HEIGHT>
• Transactions <BLOCK_EXPLORER_URL>/tx/<TX_HASH>
• Accounts <BLOCK_EXPLORER_URL>/address/<ACCOUNT_ADDRESS>
• Tokens <BLOCK_EXPLORER_URL>/token/<TOKEN_ADDRESS>

​

UTM tags

We encourage adding UTM tags with your project information to Blockscout links. This helps us track referrals and improve our overall performance via metrics. Simply append ?utm_source=<your_project_name> to the end of any links pointing to Blockscout. For example, https://eth.blockscout.com/?utm_source=tenderly.

​

Common chain replacements

Replace the Etherscan url in your code with the Blockscout url for a seamless transition. All chains supported by Etherscan are also supported by Blockscout (along with many additional Blockscout chains). Some examples are below. For additional Blockscout chains see the chains and projects page or the chainscout json file which includes chainids.

​

Exceptions

Some newer operations without standards are still handled differently by different explorers. For example:

• Blobs on Blockscout are accessed in different ways depending on the route. For example via the ?tab=blob_txs query string following a block (https://eth.blockscout.com/block/20822532?tab=blob_txs) or the ?tab=blobs query string following a transaction. Blobs on Etherscan are accessed via #blobinfo query string following a block (i.e. https://etherscan.io/block/20822532#blobinfo).
• User Operations (EIP-4337) are displayed on Blockscout via the https://eth.blockscout.com/ops url. On Etherscan there is currently no defined route, but User Operations can be viewed with the Handle Ops filter applied to the sender’s address (i.e. https://etherscan.io/advanced-filter?fadd=0x20e9695f25413f14e5807b530D0698bd4F155074&mtd=0x1fad948c~Handle+Ops&ps=10&p=8)

​

Replace the API link

Etherscan uses a subdomain link for api access. For example, for the Ethereum explorer the api link is https://api.etherscan.io/ followed by your query, or for Optimism it is https://api-optimistic.etherscan.io/ followed by your query. To replace, use the PRO API base URL with the target chain’s chain_id, swapping Etherscan’s chainid parameter for Blockscout’s chain_id: Standard API routes on Etherscan work for your queries on Blockscout. We’ve structured our data calls to be consistent with Etherscan whenever possible. Swap chain_id to move between chains, for example chain_id=8453 for Base or chain_id=10 for Optimism. You can see supported calls in the PRO API reference.

​

API Exceptions

• Blockscout does not currently support most Etherscan API PRO queries.
• Rate limits scale with your PRO API plan. See the PRO API overview for plan details and credit costs.

​

Replace your wallet block explorer link

Every wallet handles the explorer link differently, but typically wallets ship with Etherscan links by default. To change, simply go to settings and replace the Etherscan link with the Blockscout one. Here’s how you do it in MetaMask.

1. Open MetaMask, click the dots to open the menu, and select Settings
2. Select Networks
3. Select the network where you want to change the explorer link

4. Find the block explorer url (i.e. https://optimistic.etherscan.io/).
5. Change the url to Blockscout (i.e. https://optimism.blockscout.com/) and Save.