RPC method

eth_getLogs on Sei

Supported on SwiftNodes

Measured 2026-10-11 by our weekly probe, which calls eth_getLogs through the same Sei endpoint customers use.

What eth_getLogs does

Returns the event logs that match a filter: a block range, optional contract addresses and up to four topics. It is how indexers, dashboards and wallets read transfers, swaps and other contract events.

eth_getLogs on Sei: what we measured

Measured block-range cap: 1,000 blocks per call. Wider ranges are rejected; page through history in windows below the cap and filter by address where you can.
The finalized tag tracks the head on Sei (instant finality), so results at "latest" do not get reorganised.

Example request

curl -s https://rpc.swiftnodes.io/rpc/sei?key=YOUR_API_KEY \
  -X POST -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getLogs","params":[{"fromBlock":"latest","toBlock":"latest"}]}'

import { createPublicClient, http } from "viem";

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

// Any JSON-RPC method, typed loosely: eth_getLogs on Sei
const result = await client.request({
  method: "eth_getLogs",
  params: [{"fromBlock":"latest","toBlock":"latest"}],
});

Other methods on Sei

eth_getLogs on other chains

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

Frequently asked questions

Does Sei support eth_getLogs?

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

Are there limits on eth_getLogs on Sei?

Measured block-range cap: 1,000 blocks per call. Wider ranges are rejected; page through history in windows below the cap and filter by address where you can.

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

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