eth_call

eth_call executes a read-only message call against the Avalanche C-Chain EVM without broadcasting a transaction or spending any AVAX. The node simulates the call against a chosen block's state and returns the function's raw output, so it is the workhorse behind every "view" lookup on Avalanche — token balances, DEX prices, allowance checks. Point it at https://avalanche.therpc.io/YOUR_API_KEY (chain ID 43114) and nothing is written to the chain; you only read its state.

Use cases

Read ERC-20 fields such as balanceOf, decimals, symbol, or totalSupply for tokens like USDC or WAVAX on the C-Chain.
Query DEX pool reserves or spot prices from Trader Joe, GMX, or an Aave market without sending a transaction.
Simulate a swap or deposit outcome before signing it to catch reverts early and save the AVAX you would have burned on a failed send.
Apply state overrides (third argument) to test what-if scenarios — e.g. pretend an account holds more AVAX — without touching real 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://avalanche.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 Avalanche 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 can shift between your call and actual transaction inclusion; with ~1–2s C-Chain blocks the window is short but real, so do not treat the result as a settlement guarantee.
State overrides are not supported by every provider; detect the failure and fall back to a plain call rather than assuming the override applied.
Reverts come back as JSON-RPC errors (code 3 or -32000), not as a special field in the result — always handle the error path and decode the revert reason from the error data.

Supported networks

Mainnet — Chain ID: 43114
Fuji

#	الاسم	النوع	مطلوب	الوصف
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://avalanche.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 can shift between your call and actual transaction inclusion; with ~1–2s C-Chain blocks the window is short but real, so do not treat the result as a settlement guarantee.

State overrides are not supported by every provider; detect the failure and fall back to a plain call rather than assuming the override applied.

Reverts come back as JSON-RPC errors (code 3 or -32000), not as a special field in the result — always handle the error path and decode the revert reason from the error 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