Skip to main content
Flashblocks-enabled chains stream pre-confirmations every few hundred milliseconds, so your app can show transaction results well before the next full block is sealed. This guide shows how to read that pre-confirmed state over standard Ethereum JSON-RPC and from the viem and ethers libraries. For how Flashblocks work under the hood, see the Flashblocks explainer. Integration is designed to be simple and low-friction. Most apps benefit with minimal code changes.
  • In production, point your app to a Flashblocks‑aware RPC endpoint from your provider of choice. If your provider doesn’t support flashblocks yet, let us know on Discord and we’ll work with them to get it added.
  • Alternatively, you can run your own flashblocks-aware node using Base’s reth image.

Supported RPC methods

Developers can access Flashblocks using the same familiar Ethereum JSON-RPC calls. The difference is using the “pending” tag in some of them to explicitly query the pre-confirmed state instead of the last finalized block.
  • eth_getBlockByNumber: Use the pending tag to retrieve the latest flashblock snapshot.
  • eth_call: Use the pending tag to execute calls against the most recent pre-confirmed state.
  • eth_estimateGas: With pending, estimates gas usage against the latest Flashblock
  • eth_getBalance / eth_getTransactionCount: Use the pending tag to fetch balances or transaction counts respectively as they evolve within the block window. Other methods, like eth_getTransactionReceipt, eth_getTransactionByHash or eth_simulateV1, return data from pre-confirmed transactions without requiring the pending tag. Consult the Flashblocks specification for more details on each of these methods.

Libraries

You will need a Flashblocks‑aware RPC endpoint to use the following libraries:

Viem

Ethers

Next steps