RPC method

eth_feeHistory on Base

Supported on SwiftNodes

Measured 2026-10-04 by our weekly probe, which calls eth_feeHistory through the same Base 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 Base: what we measured

  • With 2.0 s blocks, a 20-block window covers about 40 seconds of Base fee history.

Example request

curl -s https://rpc.swiftnodes.io/rpc/base?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/base?key=YOUR_API_KEY") });

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

Other methods on Base

eth_feeHistory on other chains

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

Frequently asked questions

Does Base support eth_feeHistory?

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

Are there limits on eth_feeHistory on Base?

With 2.0 s blocks, a 20-block window covers about 40 seconds of Base fee history.

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

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