Overview
Note about how we calculate transaction fees on Arbitrum:Generally, the
fees_paid in our transaction response is simply the product of gas_price and gas_spent .However for Arbitrum, the fees_paid in our transaction response is the sum of multiple L1 and L2 fees associated with the function call, transaction execution and storage.To calculate the same fees_paid provided in our transaction response from Arbiscan , take the product of their Gas Price Bid and Gas Usage.Supported APIs
Foundational API
Access structured historical blockchain data across 100+ chains using REST APIs.
Get token balances, transaction histories, decoded event logs, NFT assets, token holders and more.
Use cases: Wallets, portfolio trackers, crypto accounting & tax tools, and DeFi dashboards.
Use cases: Wallets, portfolio trackers, crypto accounting & tax tools, and DeFi dashboards.
JSON-RPC
Low-latency EVM JSON-RPC with global failover and archive depth.
Point your existing tooling at the GoldRush endpoint — no code changes required.
Use cases: dApps, wallets, indexers, bots, and trading infrastructure.
Use cases: dApps, wallets, indexers, bots, and trading infrastructure.
Mainnet
API Usage
To use this blockchain network in GoldRush API calls, use:Chain Name
arbitrum-mainnet(mainnet)
Example API Calls
SDK Usage
Foundational API Support
This chain supports 24 GoldRush Foundational APIs:Wallet API
- Token Holders API on Arbitrum
- ERC-20 Token Balance API on Arbitrum
- Native Token Balance API on Arbitrum
- Historical Portfolio Value API on Arbitrum
- ERC-20 Token Transfers API on Arbitrum
NFT API
Pricing API
Security API
Transactions API
- Transaction API on Arbitrum
with-input-datawith-internal - Wallet Transaction Summary API on Arbitrum
- Earliest Wallet Transactions API on Arbitrum
with-input-datawith-internal - Wallet Transaction History API on Arbitrum
with-input-datawith-internal - Paginated Wallet Transactions API on Arbitrum
with-input-datawith-internal - Time Bucket Transactions API on Arbitrum
- Block Transactions API on Arbitrum
- Block Transactions API by Page on Arbitrum
Block Explorer API
- Block API on Arbitrum
- Block Heights API on Arbitrum
- Chain Status API on Arbitrum
- Contract Event Logs API on Arbitrum
- Event Logs API on Arbitrum
- Event Logs by Topic Hash API on Arbitrum
- Gas Price API on Arbitrum
- Supported Chains API on Arbitrum
Internal Transactions (with-internal)
Arbitrum supports internal transactions (traces). The Transactions API endpoints marked with-input-data with-internal above accept the with-internal=true query parameter, which includes internal transactions (the value transfers triggered by contract execution that are not recorded as standalone onchain transactions) in the response.
Internal transactions are included in the response by passing
with-internal and cost 0.05 credits/item.Example API Call
Recent transactions with internal transactions
JSON-RPC
Arbitrum is available on the GoldRush JSON-RPC service. Point your existing EVM tooling (ethers.js, viem, web3.js, or raw HTTP) at the GoldRush endpoint — the standardeth_*, net_*, web3_*, debug_*, and trace_* methods are supported.
Endpoint
Example JSON-RPC Calls
Sample Methods
- eth_blockNumber on Arbitrum
- eth_getBalance on Arbitrum
- eth_call on Arbitrum
- eth_getLogs on Arbitrum
- eth_getTransactionReceipt on Arbitrum