Migration Guide: BSCScan API to BSCTrace API via MegaNode

Action Required: If you're still using deprecated BSCScan APIs, you must migrate your endpoints and API keys. A recommended alternative is the BSCTrace API via MegaNode.

Start your migration today by signing up at MegaNode Dashboard and exploring the comprehensive documentation.

Explorer Overview

Below is a comparison of the two most commonly used block explorers, BSCScan (now unified under Etherscan API V2) and BSCTrace.

Explorer	BSCScan	BSCTrace
Description	Previously BSCScan; now unified under Etherscan API V2	Independent BNB Chain explorer with APIs powered by MegaNode
API free tier	No free tier for BNB Chain after deprecation	Available
API paid tier	4 tiers	1 tier
Supported Features	Standard Etherscan API modules & proxy actions	Standard RPC + enhanced MegaNode APIs
Status	BSCScan APIs deprecated; migration is mandatory	Active and fully supported
Documentation	Etherscan API Docs	MegaNode Docs and Dashboard

Why Migrate to BSCTrace?

With BSCScan APIs deprecated and Etherscan API V2 offering no free tier for BNB Chain, developers risk broken integrations and fewer affordable options for accessing essential on-chain data.

BSCTrace, powered by MegaNode, provides a practical alternative: a free tier for BNB Chain, predictable pricing, enhanced APIs for richer data access, full JSON-RPC 2.0 compatibility and high-performance infrastructure optimized specifically for BNB Chain workloads.

For most teams, it’s the simplest and most cost-efficient path to maintain continuity and reliable API performance.

Get Started with BSCTrace

1. Sign up at MegaNode Dashboard
2. Create an API key for BNB Chain
3. Review documentation
4. Choose a plan that fits your needs at Pricing Plans

API Structure Overview 

With BSCScan APIs being deprecated, you must migrate to either Etherscan API V2 or BSCTrace via MegaNode. The table below outlines the key structural differences between the two options.

Aspect	Etherscan API V2 (Replaced BSCScan)	BSCTrace/MegaNode
Protocol	REST (HTTP GET)	JSON-RPC 2.0 (HTTP POST)
Base URL	https://api.etherscan.io/v2/api	https://bsc-mainnet.nodereal.io/v1/YOUR_API_KEY
Authentication	API key as query parameter (apikey=...)	API key in endpoint URL path
Chain Selection	chainid query parameter (required)	Chain-specific endpoint URL
Method Naming	Module-based actions (module=account&action=balance)	Standard RPC method names (method=eth_getBalance)
Request Format	Query string parameters	JSON body with method, params, id
Response Structure	{"status":"1","message":"OK","result":"..."}	{"jsonrpc":"2.0","id":1,"result":"..."}
Error Handling	Status field in response (status: "0")	Error object in JSON-RPC format
HTTP Method	GET	POST

API Method Comparison

Migration Mapping Examples:

Etherscan API V2	BSCTrace/MegaNode
module=account&action=balance	eth_getBalance (JSON-RPC)
module=proxy&action=eth_blockNumber	eth_blockNumber (JSON-RPC)
module=proxy&action=eth_BlockByNumber	eth_getBlockByNumber (JSON-RPC)
module=proxy&action=eth_TransactionReceipt	eth_getTransactionReceipt (JSON-RPC)
module=account&action=txlist	nr_getAssetTransfers (Enhanced API)

Note: Many Etherscan API V2 proxy endpoints map directly to standard RPC methods, but the enhanced APIs (like transaction history) are better handled by MegaNode's enhanced APIs for improved performance.

Key Examples

The following examples show the migration path from the deprecated BSCScan APIs to BSCTrace API via MegaNode.

Example 1: Getting Native Balance

On Etherscan API V2 (Replaced BSCScan APIs)

For BNB Chain (chainid=56):

Shell curl "https://api.etherscan.io/v2/api?apikey=YOUR_API_KEY&chainid=56&module=account&action=balance&address=0xfF3f428583c15a5681584e9e5e86e270418AC4d3&tag=latest"

Response:

JSON {   "status": "1",   "message": "OK",   "result": "0" }

Key Points:

• Uses unified api.etherscan.io/v2/api endpoint
• Requires chainid parameter to specify the chain (1 for Ethereum, 56 for BNB Chain)
• API key passed as query parameter
• Response format: status, message, and result fields
• Result is returned as a string (hexadecimal for balances)

On BSCTrace API via MegaNode

Shell curl -X POST https://bsc-mainnet.nodereal.io/v1/YOUR_API_KEY \   -H "Content-Type: application/json" \   -d '{     "jsonrpc": "2.0",     "method": "eth_getBalance",     "params": [       "0xfF3f428583c15a5681584e9e5e86e270418AC4d3",       "latest"     ],     "id": 1   }'

Response:

JSON {   "jsonrpc": "2.0",   "id": 1,   "result": "0x18b907bc31ae8172d100e0" }

Key Points:

• Standard JSON-RPC 2.0 protocol
• Chain-specific endpoint URL (no need for chainid parameter)
• API key embedded in endpoint path
• Result returned as hexadecimal string with 0x prefix
• Standard JSON-RPC response format with jsonrpc, id, and result fields

Example 2: Getting Transaction History

Etherscan API V2 (Replaced BSCScan APIs)

For BNB Chain (chainid=56):

Shell curl "https://api.etherscan.io/v2/api?apikey=YOUR_API_KEY&chainid=56&module=account&action=txlist&address=0xfF3f428583c15a5681584e9e5e86e270418AC4d3&startblock=0&endblock=99999999&page=1&offset=10&sort=asc"

Key Differences from Old BSCScan:

• Uses api.etherscan.io/v2/api instead of api.bscscan.com/v2/api
• Requires chainid=56 parameter for BNB Chain
• Same module/action structure but unified endpoint

BSCTrace API via MegaNode (Enhanced API)

Shell curl -X POST https://bsc-mainnet.nodereal.io/v1/YOUR_API_KEY \   -H "Content-Type: application/json" \   -d '{     "jsonrpc": "2.0",     "method": "nr_getAssetTransfers",     "params": [{       "fromAddress": "0xfF3f428583c15a5681584e9e5e86e270418AC4d3",       "category": ["external", "internal", "erc20", "erc721", "erc1155"],       "withMetadata": true,       "excludeZeroValue": false,       "pageSize": 10,       "pageToken": ""     }],     "id": 1   }'

Supported & Unsupported API Lists

The supported API list shows which deprecated BSCScan endpoints map directly to MegaNode equivalents, while the unsupported list highlights APIs requiring off-chain aggregation or external data.

Together, they provide a clear view of what can be migrated and what may need alternative solutions.

Conclusion

With BSCScan APIs now deprecated and replaced by Etherscan API V2, migrating to BSCTrace API via MegaNode is a smart alternative that provides:

• Immediate migration path: No need to wait for Etherscan API V2 migration - migrate directly to BSCTrace API
• Cost savings: More accessible pricing compared to Etherscan API V2's paid-only model for BNB Chain
• Better features: Enhanced APIs with additional functionality beyond standard RPC
• Standard compliance: Full JSON-RPC 2.0 compliance for better interoperability
• Better BNB Chain support: Optimized specifically for BNB Chain's needs

Most deprecated BSCScan APIs have direct equivalents in MegaNode, making migration straightforward. For APIs requiring contract verification services, you may need to deploy your own verification infrastructure or use alternative solutions.

Start your migration today by signing up at MegaNode Dashboard and exploring the comprehensive documentation.