Link to Blockscout
Easily replace your current explorer links with Blockscout explorer links
Last updated
Was this helpful?
Easily replace your current explorer links with Blockscout explorer links
Last updated
Was this helpful?
In most cases simply replacing the first part of the url is all that is needed to replace Etherscan with Blockscout.
For example, replace with in your code and the corresponding links to blocks, transactions, etc will be mapped to Blockscout rather than Etherscan.
😢 Tx before replacement 😁 Tx after replacement
Blockscout linking architecture follows 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>
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
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 page or the .
Ethereum
Ethereum Sepolia
Optimism
Optimism Sepolia
Base
Base Sepolia
Arbitrum
Arbitrum Sepolia
Polygon
Gnosis
Celo
Unichain
Some newer operations without standards are still handled differently by different explorers. For example:
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.
Open MetaMask, click the dots to open the menu, and select Settings
Select Networks
Select the network where you want to change the explorer link
Repeat this process for all networks from the Networks screen.
Blobs on Blockscout are accessed in different ways depending on the route. For example via the ?tab=blob_txs query string following a block () or the ?tab=blobs query string following a transaction. Blobs on Etherscan are accessed via #blobinfo query string following a block (ie ).
User Operations (EIP-4337) are displayed on Blockscout via the url. On Etherscan there is currently no defined route, but User Operations can be viewed with the Handle Ops filter applied to the senders address (ie )
Standard Blockscout RPC calls do not need an API key (Etherscan calls always require one). You can remove the &apikey=YourApiKeyToken query string at the end of the url with no problem or keep it as any string value and Blockscout will process. If you want to increase your limits, you can also and use it to access 10 RPS limits.
Etherscan uses a subdomain link for api access. For example, the Ethereum explorer the api link is followed by your query, or for Optimism it is followed by your query.
To replace, simply use the regular blockscout url for the instance, for example for Ethereum or for Optimism.
😢 API call before replacement (doesn't work without API key)
😁 API call after replacement (works without API key)
Standard API routes on Etherscan work for your queries on Blockscout. We've structured our data calls to be consistent with Etherscan whenever possible. You can see supported calls in the .
If you require more varied or richer datasets consider replacing your JSON RPC calls with the . This free API features additional metadata, stats data, human readable transactions and more.
Blockscout does not currently support most queries.
The 10 RPS limits can be increased further via the .
Find the block explorer url (ie ).
Change the url to blockscout (ie ) and Save.
