Link to OpenScan.AI

Replace the primary explorer link

In most cases simply replacing the first part of the URL is all that is needed to replace another explorer with OpenScan.AI.

For example, replace https://etherscan.io/ with https://xdcscan.io/ in your code and the corresponding links to blocks, transactions, etc. will be mapped to OpenScan.AI rather than Etherscan.

Tx before replacement:

https://etherscan.io/tx/0x3e8c3aad50b2f8471400e3fe6b812f20c332846064dff8c25fadf783eefa68df

Tx after replacement:

https://xdcscan.io/tx/0x3e8c3aad50b2f8471400e3fe6b812f20c332846064dff8c25fadf783eefa68df

OpenScan.AI’s linking architecture follows the EIP-3091 standard 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 OpenScan.AI 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 OpenScan.AI. For example https://xdcscan.io/?utm_source=tenderly.

Common chain replacements

Replace the legacy explorer URL in your code with the OpenScan.AI URL for a seamless transition.

Exceptions

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

• User Operations (EIP-4337) are displayed on OpenScan.AI via the https://xdcscan.io/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.

Replace the API link

Standard OpenScan.AI 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 OpenScan.AI will process it. If you want to increase your limits, you can also sign up for a free OpenScan.AI API key and use it to access higher RPS limits.

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, simply use the regular OpenScan.AI URL for the instance, for example https://xdcscan.io/.

API call before replacement (doesn’t work without API key):

https://api.etherscan.io/api?module=account&action=balance&address=0xde0b295669a9fd93d5f28d9ec85e40f4cb697bae&tag=latest&apikey=YourApiKeyToken

API call after replacement (works without API key):

https://xdcscan.io/api?module=account&action=balance&address=0xde0b295669a9fd93d5f28d9ec85e40f4cb697bae&tag=latest

Standard API routes on Etherscan work for your queries on OpenScan.AI. We’ve structured our data calls to be consistent with Etherscan whenever possible. You can see supported calls in the JSON RPC & ETH-compatible RPC endpoints section of the API documentation.

If you require more varied or richer datasets, consider replacing your JSON RPC calls with the REST API from OpenScan.AI. This free API features additional metadata, stats data, human-readable transactions, and more.

API Exceptions

• OpenScan.AI does not currently support most Etherscan API PRO queries.

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 OpenScan.AI 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 (e.g. https://etherscan.io/).
5. Change the URL to OpenScan.AI (e.g. https://xdcscan.io/) and save.

Repeat this process for all networks from the Networks screen.