RPC method

eth_feeHistory on Avalanche

Supported on SwiftNodes

Measured 2026-10-04 by our weekly probe, which calls eth_feeHistory through the same Avalanche endpoint customers use.

What eth_feeHistory does

Returns base fees, gas-used ratios and optional priority-fee percentiles for a range of recent blocks. Wallets and SDKs use it to set maxFeePerGas and maxPriorityFeePerGas instead of guessing from eth_gasPrice.

eth_feeHistory on Avalanche: what we measured

  • With 1.3 s blocks, a 20-block window covers about 26 seconds of Avalanche fee history.

Example request

curl -s https://rpc.swiftnodes.io/rpc/avalanche?key=YOUR_API_KEY \
  -X POST -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_feeHistory","params":["0x14","latest",[25,50,75]]}'
import { createPublicClient, http } from "viem";

const client = createPublicClient({ transport: http("https://rpc.swiftnodes.io/rpc/avalanche?key=YOUR_API_KEY") });

// Any JSON-RPC method, typed loosely: eth_feeHistory on Avalanche
const result = await client.request({
  method: "eth_feeHistory",
  params: ["0x14","latest",[25,50,75]],
});

Other methods on Avalanche

eth_feeHistory on other chains

Support differs by chain; the full measured table is on the eth_feeHistory reference.

Frequently asked questions

Does Avalanche support eth_feeHistory?

Yes. eth_feeHistory answered correctly on the SwiftNodes Avalanche endpoint in our weekly method probe (2026-10-04), which sends real requests through the customer path.

Are there limits on eth_feeHistory on Avalanche?

With 1.3 s blocks, a 20-block window covers about 26 seconds of Avalanche fee history.

Avalanche endpoints, live block height and WebSocket status are on the Avalanche RPC page.

One key covers every chain we serve, and SwiftNodes has a free tier.