Optimized submission
Send Arbitrum mainnet transactions through a private, optimized path to reduce inclusion delays. Works with your existing HTTPS and WebSocket endpoints.
Read pool state, simulate trades, and send transactions with reliable, high-performance Arbitrum One RPC infrastructure.

Connect to Arbitrum One through one geo-balanced endpoint. Read pool state, follow contract events, and submit transactions through the nearest available region, with no manual routing or extra setup.
Submit transactions, query historical state, trace Nitro execution, and scale DeFi workloads with one Arbitrum development stack.
Send Arbitrum mainnet transactions through a private, optimized path to reduce inclusion delays. Works with your existing HTTPS and WebSocket endpoints.
Scale high-volume RPC workloads with consistent performance, unlimited requests within your RPS tier, and predictable monthly costs.
Query past ETH balances, token balances, pool state, and contract storage. Backfill Arbitrum history for DeFi analytics, portfolio reporting, and reconciliation.
Inspect Nitro transactions with debug_traceTransaction and debug_traceCall. Diagnose reverted swaps, inspect internal calls, and investigate smart contract behavior.
Read liquidity pools, simulate swaps with eth_call, and submit signed transactions. Build bots and dashboards around Arbitrum markets such as GMX, Pendle, and Camelot.
Explore Arbitrum developer tools (opens in a new tab)Backfill contract events with eth_getLogs and query historical state through archive RPC. Track positions, vault activity, and transaction histories for analytics.
Explore Arbitrum archive data (opens in a new tab)Read ETH and ERC-20 balances, check allowances, and follow transaction receipts. Connect ethers.js, viem, or web3.py to Arbitrum One or Sepolia.
Get an Arbitrum RPC endpointMonitor token transfers, reconcile account balances, and verify contract execution. Build reliable data pipelines for tokenized assets, treasury tools, and stablecoin payments.
Explore Arbitrum infrastructure for RWA (opens in a new tab)Deploy an Arbitrum endpoint through Chainstack MCP. Give agents access to contract reads, transaction simulations, and signed transaction submission.
Explore Chainstack AI tools (opens in a new tab)Run Arbitrum One indexers, DeFi backends, and tokenized-asset applications on isolated compute and storage. Choose full or archive infrastructure, with Chainstack managing deployment, upgrades, and Nitro node maintenance. Discuss custom Stylus tracing with our team for Enterprise deployments.
Select Arbitrum One mainnet or Sepolia and choose full or archive mode to see current monthly infrastructure pricing.
Feedback from teams using Arbitrum and multichain infrastructure for security, wallets, analytics, and trading.
Compare Chainstack’s Arbitrum RPC response times and request success rates against other providers across Europe, the US, and Asia. Explore P50, P95, and P99 latency in Chainstack Compare.
Compare Arbitrum RPC providers (opens in a new tab)Run Arbitrum One mainnet or Sepolia nodes on infrastructure you control. Deploy Nitro through Chainstack Self-Hosted, with monitoring, automated updates, and self-healing operations. Connect an Ethereum execution and beacon endpoint for the matching parent network.

Get free Ethereum Sepolia ETH from the Chainstack faucet, then bridge it to Arbitrum Sepolia through the official Arbitrum bridge. Use your Arbitrum Sepolia RPC endpoint to deploy contracts, simulate swaps, and test transactions with ethers.js, viem, Hardhat, or Foundry.
The Chainstack Sepolia faucet tops up eligible wallets to 0.5 Sepolia ETH every 24 hours. Bridge part of that test ETH to Arbitrum Sepolia and keep some on Sepolia for the bridge transaction fee.
Start with free Arbitrum RPC for One mainnet and Sepolia. Scale DeFi applications with archive data, transaction tracing, and dedicated infrastructure.
Includes:
All Developer features, plus:
Add-ons and Dedicated Node infrastructure are billed separately.
Explore Arbitrum RPC providers, tokenized-asset infrastructure, endpoint setup, and L2 comparisons.

Compare Arbitrum RPC providers for DeFi and production workloads.
Read article
Choose Arbitrum infrastructure for tokenized assets and financial applications.
Read article
Deploy an Arbitrum One or Sepolia endpoint and connect your application.
Read article
Compare Arbitrum and Optimism for production RPC workloads.
Read articleConnect your application to a Chainstack Arbitrum HTTPS endpoint to read ETH and token balances, call smart contracts, retrieve event logs, estimate gas, and submit signed transactions. Common methods include eth_getBalance, eth_call, eth_getLogs, eth_estimateGas, and eth_sendRawTransaction. Use WebSocket eth_subscribe subscriptions for new blocks and contract logs. Arbitrum One uses chain ID 42161; Arbitrum Sepolia uses 421614. Both use ETH for gas.
Integrate your endpoint with ethers.js or viem for JavaScript and TypeScript, web3.py for Python, and Hardhat or Foundry for contract development. See the Arbitrum API reference and Arbitrum tooling guide for supported methods and integration examples.
Arbitrum Nitro uses debug_* methods for blocks from 22,207,815 onward, while arbtrace_* methods apply to pre-Nitro blocks. The Ethereum trace_* namespace is not available. Customized Enterprise Dedicated Nodes can expose stylusTracer for Stylus execution traces. Check the Arbitrum methods reference before choosing a tracing method. Arbitrum’s sequencer feed is separate from standard JSON-RPC WebSocket subscriptions.