Documentation - Dexalot Testnet Network (ALOT) Blockchain Explorer

TPS: 0.2

Welcome to the Routescan APIs documentation 🚀

Routescan is the first multichain ecosystem explorer, search, API, and analytics platform for all major EVM (Ethereum Virtual Machine) chains, including Ethereum, Avalanche, Metis, Boba and others. With its comprehensive tools and user-friendly interface, Routescan offers unparalleled insights into various blockchain networks, enhancing transparency and promoting a deeper understanding of decentralized ecosystems.

To ensure equal access to blockchain information, we've designed the Routescan Developer APIs. This allows developers to tap directly into Routescan's block explorer data and services through GET/POST requests.

Routescan's APIs are provided as a community service and without warranty, so please use what you need and no more.

Fast APIs

At Routescan, we've engineered high-speed REST APIs that offer results in near real-time. Whether you're aiming to retrieve ERC20 transfers, NFT movements, or the latest transactions with minimal latency and delay, our REST APIs are the go-to solution. Additionally, you can fetch balances, token holdings, and more with ease.

Etherscan compatibility

At Routescan, we understand the importance of seamless transitions and the value of pre-existing code. Therefore, to assist developers and facilitate smoother migrations of dApps, we've structured our data from all EVM chains indexed by Routescan to align with Etherscan's API format.

This compatibility ensures that developers can effortlessly recycle older codebases and integrate them into new or expanding projects, eliminating the need to start from scratch and thereby optimizing development time and resources.

API Plans

Free Tier

Our free tier allows you to access blockchain data without needing an API key at all. This tier supports up to 2 requests per second (rps) and a daily limit of 10000 calls, making it perfect for developers or users starting out or working on projects with moderate API usage.

Note: Normally, requests will go through even without any placeholders. Placeholders are only necessary for certain integrations where including a key parameter in the query, config files, or similar is required. You can use any API key value in query parameters: &apikey=placeholder. Or in configs: apiKey: { routescan: "placeholder" }.

Please be aware that not all chains are available under the free tier, and some chains may not be fully indexed, which could result in incomplete data. For the most current information on free tier access and indexing, see our free plan chain list: https://docs.routescan.io/api-access.

Paid Plans

For higher usage volumes, advanced features, and full access to all supported EVM chains, we offer paid plans that require an API key.

With one API key, you can:

Access all chains we index*
Use the /all parameter to retrieve data across all supported chains (exclusive to paid plans)
Benefit from increased rate limits, higher daily call volumes, and priority support
Simplify your development process with seamless multichain integration

Free$0/mo

2 calls/secondup to 10,000 calls/day

Standard $160/mo

$2400$1920/yr

10 calls/second up to 200.000 calls/day Priority support

Advanced $240/mo

$3600$2880/yr

20 calls/second up to 500.000 calls/day Priority support

Recommended

Professional $320/mo

$4800$3840/yr

30 calls/second up to 1.000.000 calls/day Priority support

Pro Plus $440/mo

$6600$5280/yr

30 calls/second up to 1.500.000 calls/day Priority support

Source attribution via a backlink or a mention that your app is "Powered by Routescan.io APIs" is required for FREE plan except for personal/private usage

Custom plans with enhanced limits and features are also available. Contact us at hello@routescan.io for more details.

Already have an API plan?

Log in to the portal with your associated email address and a one-time passcode to manage your subscription.
https://billing.stripe.com/p/login/7sI2bvgk22LS10s9AA

* Please note that some chains may not be fully indexed and could return incomplete data. For the latest details on indexing status, please refer to the list at the following link: https://docs.routescan.io/api-access