Read contract state, connect wallets, and send transactions with reliable, high-performance Avalanche C-Chain RPC infrastructure.
Connect to Avalanche C-Chain mainnet or Fuji through one geo-balanced endpoint. Read AVAX balances, call Solidity contracts, and track transactions through the nearest available region.
Scale Avalanche applications with predictable capacity, archive data, and transaction debugging.
Scale high-volume RPC workloads with consistent performance, unlimited requests within your RPS tier, and predictable monthly costs.
Read historical AVAX balances, contract state, and event logs on C-Chain. Backfill DeFi data, wallet activity, and financial records with archive access.
Inspect C-Chain execution with debug_traceTransaction and debug_traceCall. Diagnose reverted swaps and internal calls using supported debug methods on archive nodes.
Read liquidity-pool and lending-market state, simulate contract calls, and submit signed C-Chain transactions. Use ethers.js, viem, Hardhat, or Foundry with your Avalanche endpoint.
Explore Avalanche tooling
Read AVAX and token balances, estimate fees, and track transaction receipts. Build wallet interfaces and stablecoin payment backends with familiar EVM libraries.
Get an Avalanche RPC endpoint
Backfill contract events and retrieve historical balances and state with archive access. Power portfolio reporting, analytics, and application recovery without operating an archive node.
Explore Avalanche APIs
Inspect execution traces to investigate reverted swaps, contract calls, and internal transfers. Use supported debug methods with a paid-plan archive node.
Explore Avalanche debug APIs
Query staking and validator information through P-Chain APIs. Use separate C-Chain, X-Chain, and P-Chain paths for the data each part of your application needs.
Explore Avalanche methodsRun DeFi backends, indexers, and financial applications on isolated compute and storage. Choose an available Avalanche mainnet or Fuji configuration, with Chainstack managing deployment, upgrades, and node operations.
Choose Avalanche mainnet or Fuji and an available node mode to see monthly infrastructure pricing.
Save over 50% on our elite pay as you go plan
Chat on Telegram (opens in a new tab)Feedback from Benqi’s Avalanche infrastructure work and teams building wallets, security tools, and trading applications across supported networks.
Our collaboration with Chainstack marks a pivotal step in enhancing the Avalanche ecosystem, offering a seamless experience for deploying Subnets.Chainstack’s robust infrastructure has significantly enhanced our ability to secure Web3 environments effectively.Chainstack has been crucial in enhancing Brave Wallet’s multi-chain functionality and UX.The Unlimited Node flat-fee model gives us cost predictability, and the performance is rock-solidWe’ve gone from weekly incidents to zero incidents.Build on geo-balanced Avalanche endpoints for C-Chain mainnet and Fuji. Scale sustained RPC workloads with flat-fee Unlimited Node capacity, or choose Dedicated Nodes for isolated infrastructure.
Get an Avalanche endpointRun Avalanche mainnet or Fuji nodes on infrastructure you control. Deploy AvalancheGo through Chainstack Self-Hosted, with monitoring, automated updates, and self-healing operations.
Read an AVAX balance on Avalanche C-Chain with eth_getBalance. Use the same JSON-RPC request on mainnet or Fuji.
AI-ready infrastructure
Refer and earn
Ethereum
Hyperliquid
Solana
Arbitrum
BNB Smart Chain
Base
Polygon
TRON
Sui
Robinhood
SOC 2 Type II
ISO 27001
99.99%+ uptime
Learn more
View installation guidehttps://avalanche-mainnet.core.chainstack.com/ext/bc/C/rpc/YOUR_ENDPOINT_IDwss://avalanche-mainnet.core.chainstack.com/ext/bc/C/ws/YOUR_ENDPOINT_ID43114 · AVAXCopy your C-Chain URL from Access and credentials. Replace YOUR_ENDPOINT_ID with your endpoint ID. Keep /ext/bc/C/rpc before the ID; P-Chain and X-Chain use different paths.
curl --request POST \
--url https://avalanche-mainnet.core.chainstack.com/ext/bc/C/rpc/YOUR_ENDPOINT_ID \
--header 'Content-Type: application/json' \
--data '{
"jsonrpc": "2.0",
"id": 1,
"method": "eth_getBalance",
"params": [
"0x38545c4b331D8BFb3bee94C62D77a6735b5eF8c0",
"latest"
]
}'The result is a hexadecimal AVAX balance in wei. One AVAX equals 10^18 wei. This request reads the latest executed state without spending AVAX.
Start with free Avalanche RPC for C-Chain mainnet or Fuji. Scale DeFi applications with archive data, debug APIs, higher throughput, and dedicated infrastructure.
Includes:
All Developer features, plus:
Add-ons and Dedicated Node infrastructure are billed separately.
Exceptional support on every paid planExplore Avalanche endpoint setup, RPC providers, validator infrastructure, and trading integrations.
Connect C-Chain, X-Chain, and P-Chain APIs to your application.
Read article
Compare node types, pricing, and developer features.
Read article
Explore the infrastructure behind Benqi’s validator deployments.
Read article
Connect automated trading workflows to managed RPC infrastructure.
Read article
Avalanche RPC is the interface applications use to read Avalanche blockchain data and submit transactions. C-Chain provides Ethereum-compatible JSON-RPC for Solidity applications, while the X-Chain and P-Chain expose different APIs. Chainstack provides managed access to Avalanche mainnet and Fuji. See the Avalanche API reference.
Create a free Chainstack account, create a project, and deploy an Avalanche Global Node on mainnet or Fuji. Open Access and credentials and copy the URL for the chain you need. The Developer plan includes 3 million request units per month, up to 25 requests per second, and one node. No credit card is required.
Your Chainstack C-Chain HTTPS URL follows https://avalanche-mainnet.core.chainstack.com/ext/bc/C/rpc/YOUR_ENDPOINT_ID for mainnet and https://avalanche-fuji.core.chainstack.com/ext/bc/C/rpc/YOUR_ENDPOINT_ID for Fuji. Copy your complete URL from Access and credentials. The chain path comes before the endpoint ID. See the Avalanche endpoint structure.
Avalanche C-Chain mainnet uses chain ID 43114 (0xa86a), and Fuji C-Chain uses 43113 (0xa869). Both use AVAX for gas. These are EVM chain IDs for C-Chain, not identifiers to reuse for every Avalanche blockchain. See the official C-Chain RPC reference.
C-Chain serves EVM smart contracts through /ext/bc/C/rpc. X-Chain serves native asset APIs through /ext/bc/X. P-Chain serves staking and validator APIs through /ext/P. On Chainstack, append the endpoint ID after the chain path. A custom Avalanche L1 can require its own RPC service; a Primary Network C-Chain endpoint does not automatically expose that L1’s state. See Avalanche endpoint paths and supported methods.
Yes. Use your C-Chain endpoint with MetaMask, ethers.js, viem, web3.py, Hardhat, or Foundry. For C-Chain subscriptions, use wss://avalanche-mainnet.core.chainstack.com/ext/bc/C/ws/YOUR_ENDPOINT_ID, or the corresponding Fuji URL from your node. HTTPS and WSS use different C-Chain paths. Follow the Avalanche tooling guide.
Call eth_getBalance on C-Chain with an EVM address and a block tag such as latest. The result is a hexadecimal balance in wei, with 10^18 wei per AVAX. It reads the address’s C-Chain AVAX balance, not ERC-20 token balances or funds on the X-Chain or P-Chain. See the Avalanche eth_getBalance reference.
Yes. Chainstack lists Avalanche archive access on Global Nodes for mainnet and Fuji, available from the Growth plan. Use archive access for historical C-Chain balances and contract state. Full requests consume 1 request unit, while archive requests consume 2. Dedicated archive configurations depend on the selected network and current availability. See supported networks and modes and request-unit rules.
Yes. Avalanche debug APIs require a paid plan and an archive node. Supported methods include debug_traceTransaction and debug_traceCall for investigating execution and contract failures. Availability follows the current AvalancheGo API surface, so do not assume every Geth debug method is supported. See Avalanche debug API requirements.
After the Helicon upgrade, latest refers to the last executed block, while safe and finalized refer to the last settled block. Choose the block tag required by your application, especially when reconciling payments or reading contract state for settlement. See the official C-Chain RPC behavior.
Start with the free Developer plan. Paid plans start at $40 per month with annual billing. Unlimited Node adds flat-fee RPC capacity from the Growth plan. Dedicated Nodes start from Pro, with infrastructure billed separately; available modes depend on the selected network. Compare plan features and current Avalanche configurations.
Yes. Chainstack Self-Hosted supports Avalanche mainnet and Fuji using AvalancheGo. It runs a non-validator full node on infrastructure you control, with monitoring, automated updates, and self-healing operations. A Primary Network node serves the built-in chains; custom Avalanche L1 tracking can require additional configuration. Check supported clients and networks and the installation guide.
Use the official Avalanche faucet for Fuji testnet tokens, subject to its eligibility requirements. Connect your application to Fuji C-Chain with chain ID 43113. Testnet AVAX has no monetary value and cannot pay mainnet fees. Chainstack’s faucet portal does not currently list Avalanche Fuji.
Connect to Avalanche C-Chain mainnet at https://avalanche-mainnet.core.chainstack.com/ext/bc/C/rpc/YOUR_ENDPOINT_ID or Fuji at https://avalanche-fuji.core.chainstack.com/ext/bc/C/rpc/YOUR_ENDPOINT_ID. Copy your complete authenticated URL from Access and credentials and replace the example endpoint ID. Keep the chain path before the ID. Mainnet uses EVM chain ID 43114; Fuji uses 43113. Both use AVAX for gas. See the Avalanche endpoint and tooling guide.
Use eth_getBalance for AVAX balances, eth_call for contract reads, eth_getLogs for events, and eth_sendRawTransaction for signed transaction submission. Native AVAX balances use 18 decimals. C-Chain WebSocket connections use /ext/bc/C/ws before the endpoint ID. X-Chain and P-Chain use their own API paths. See the Avalanche API reference and method availability.
Use archive access for historical C-Chain state and a paid-plan archive node for supported debug methods. After Helicon, latest refers to the last executed block, while safe and finalized refer to the last settled block. Select the appropriate block tag for your application. See Avalanche debug requirements and official C-Chain behavior.
