RPC method

eth_getBlockReceipts on Sei

Supported on SwiftNodes

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

What eth_getBlockReceipts does

Returns every transaction receipt in a block in one call, instead of one eth_getTransactionReceipt request per transaction. Indexers and accounting pipelines use it to read a whole block's outcomes and logs at once.

eth_getBlockReceipts on Sei: what we measured

  • 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_getBlockReceipts","params":["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_getBlockReceipts on Sei
const result = await client.request({
  method: "eth_getBlockReceipts",
  params: ["latest"],
});

Other methods on Sei

eth_getBlockReceipts on other chains

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

Frequently asked questions

Does Sei support eth_getBlockReceipts?

Yes. eth_getBlockReceipts 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_getBlockReceipts on Sei?

The finalized tag tracks the head on Sei (instant finality), so results at "latest" do not get reorganised.

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.