eth_call

eth_call executes a read-only message call against the EVM on Arbitrum One without broadcasting a transaction or spending any ETH gas. The Nitro node runs the call locally against the chosen block's state and hands back the raw return data, making it the workhorse for reading state from contracts like GMX, Uniswap, and Aave that live on the rollup. Send it to https://arbitrum.therpc.io/YOUR_API_KEY (chain ID 42161) to query any deployed contract for free.

Use cases

Read ERC-20 fields such as balanceOf, decimals, symbol, or totalSupply for any token bridged to or native on Arbitrum One.
Query DEX pool reserves or spot prices straight from Uniswap or Camelot pools to power a price feed.
Simulate a swap or GMX position change before signing so reverts surface early, before you spend ETH on the L2.
Apply state overrides (third argument) to test what-if scenarios — e.g. a hypothetical token balance — without touching live chain state.

Parameters

#	الاسم	النوع	مطلوب	الوصف
1	`transaction`	object	نعم	Transaction object. Required fields: `to` (target contract). Optional: `from` (msg.sender), `gas` (hex), `gasPrice` (hex), `value` (hex wei), `data` (ABI-encoded calldata).
2	`blockTag`	string \| object	نعم	Block at which to execute the call. Use hex block number or a named tag.الافتراضي: `latest`
3	`stateOverrides`	object	لا	Optional map of address → { balance, nonce, code, state, stateDiff } overrides applied only for this call. Not supported by all providers.

Response

النوع	الوصف
string	Hex-encoded return data from the executed function. Decode with the contract ABI. If the call reverts, an error with code -32000 or 3 is returned instead.

Example request

1curl https://arbitrum.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5    "jsonrpc": "2.0",
6    "method": "eth_call",
7    "params": [
8        {
9          "to": "0x0000000000000000000000000000000000000000",
10          "data": "0x"
11        },
12        "latest",
13        {}
14      ],
15    "id": 1
16  }'

Try it live in the Arbitrum One playground.

Errors & troubleshooting

الكود	الرسالة	السبب
`3`	`execution reverted`	The EVM reverted the call. Error data contains the revert reason.
`-32602`	`invalid argument`	Malformed transaction object or missing required `to` field.
`-32000`	`execution reverted`	Node-level revert without revert data (e.g. out-of-gas within the call, or require with no message).

Common pitfalls

State at latest reflects the sequencer's current view and can shift before your transaction is actually included — never treat an eth_call result as a settlement guarantee.
State overrides are not supported by every provider; detect the failure and fall back to a plain call when they are unavailable.
A revert surfaces as a JSON-RPC error (code 3 or -32000), not as a special result field — always handle the error path so a reverting GMX or Aave call is not mistaken for empty return data.

Supported networks

Mainnet — Chain ID: 42161
Sepolia — Chain ID: 421614

#	الاسم	النوع	مطلوب	الوصف
1	`transaction`	object	نعم	Transaction object. Required fields: `to` (target contract). Optional: `from` (msg.sender), `gas` (hex), `gasPrice` (hex), `value` (hex wei), `data` (ABI-encoded calldata).
2	`blockTag`	string \| object	نعم	Block at which to execute the call. Use hex block number or a named tag.الافتراضي: `latest`
3	`stateOverrides`	object	لا	Optional map of address → { balance, nonce, code, state, stateDiff } overrides applied only for this call. Not supported by all providers.

النوع

الوصف

string

Hex-encoded return data from the executed function. Decode with the contract ABI. If the call reverts, an error with code -32000 or 3 is returned instead.

Example request

1curl https://arbitrum.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5    "jsonrpc": "2.0",
6    "method": "eth_call",
7    "params": [
8        {
9          "to": "0x0000000000000000000000000000000000000000",
10          "data": "0x"
11        },
12        "latest",
13        {}
14      ],
15    "id": 1
16  }'

Errors & troubleshooting

الكود	الرسالة	السبب
`3`	`execution reverted`	The EVM reverted the call. Error data contains the revert reason.
`-32602`	`invalid argument`	Malformed transaction object or missing required `to` field.
`-32000`	`execution reverted`	Node-level revert without revert data (e.g. out-of-gas within the call, or require with no message).

Common pitfalls

State at latest reflects the sequencer's current view and can shift before your transaction is actually included — never treat an eth_call result as a settlement guarantee.

State overrides are not supported by every provider; detect the failure and fall back to a plain call when they are unavailable.

A revert surfaces as a JSON-RPC error (code 3 or -32000), not as a special result field — always handle the error path so a reverting GMX or Aave call is not mistaken for empty return data.

eth_call

Use cases

Parameters

Response

Example request

Errors & troubleshooting

Common pitfalls

Supported networks

See also

هل أنت مستعد لاستدعاء هذا في الإنتاج؟

eth_call

Use cases

Parameters

Response

Example request

Errors & troubleshooting

Common pitfalls

Supported networks

See also