If you have swapped on Base recently and noticed your transaction appears to confirm almost instantly, you have likely benefited from Flashblocks. This article explains what Flashblocks are, how they work, and why they matter if you use a wallet or app on Base.
The problem Flashblocks solves
Base, like most blockchains, produces new blocks on a fixed schedule. A block is a batch of transactions that gets bundled together, ordered, and added to the chain. On Base, a new block has historically been produced roughly every 2 seconds.
Two seconds sounds fast compared to older blockchains, but it is still slow compared to a card payment or a modern web app, where you expect near instant feedback. When you submit a swap, you want to know quickly whether it went through, especially if you are trading during a period of fast price movement.
Waiting for a full block to be built and confirmed adds a small but noticeable delay. Flashblocks was built to shrink that delay without changing how Base's underlying security model works.
How Flashblocks works
Flashblocks was designed and built by Flashbots for chains built on the OP Stack, the software framework that Base is built on. Instead of waiting the full 2 seconds and releasing one complete block, the block builder breaks that same 2 second window into smaller pieces called Flashblocks.
Each Flashblock is a partial, streaming update containing the transactions ordered and executed so far. A new Flashblock is issued and broadcast to nodes roughly every 200 milliseconds. Over a 2 second block window, that adds up to about 10 Flashblocks, each one appending more transactions until the full block is complete and submitted the same way blocks always have been.
In practical terms, this means a node or an app watching the network does not have to wait for the entire 2 second block to be sealed to see that your transaction was included and executed. It can see that result after the Flashblock containing your transaction is streamed out, often within a couple hundred milliseconds.
This is why the underlying mechanism is described as a preconfirmation. Flashblocks does not change when a block is finally written to the chain. It changes how quickly you can find out what is inside the next one.
What "preconfirmation" actually means
It helps to be precise about what you are seeing when a transaction feels instant. A Flashblock preconfirmation tells you that the block builder has ordered and executed your transaction as part of the block currently being assembled. It is a strong signal that your transaction succeeded and roughly what state changed as a result, for example a token balance update.
It is not the same thing as final settlement on Ethereum. Base is an Optimistic Rollup, meaning transaction batches are periodically posted to Ethereum, and there is a challenge period built into that system before a transaction is considered fully final at the Ethereum layer. Flashblocks operates entirely within Base's own block production, well before that L1 settlement step. If you want the full picture of how Base blocks eventually become final, see our article on when a Base transaction is final.
In everyday use, for something like a swap in a self-custody wallet, the Flashblock preconfirmation is generally reliable enough to treat as "it worked." For very large transfers or situations where absolute certainty matters, it is still reasonable to wait for the full block and, for high value transactions, additional confirmations.
Why this matters for swapping
Faster preconfirmations mainly show up as a better user experience. A few concrete effects:
Faster feedback in your wallet. Apps and wallets that support Flashblocks can update their interface as soon as a Flashblock confirms your transaction, rather than polling and waiting for the next full block.
Less uncertainty during fast markets. When prices are moving quickly, knowing sooner whether your swap executed, and at what result, makes it easier to decide your next move.
No change to fees or how you use Base. Flashblocks is infrastructure that runs at the network and block builder level. You do not need to configure anything, hold any additional token, or change how you send a transaction to benefit from it. It works the same way regardless of which Base wallet you use.
It is also worth noting that Flashblocks does not change gas costs. The fee you pay for a Base transaction is still made up of the L2 execution cost and the L1 data fee, the same components covered in our article on base fees, priority fees, and the L1 data fee.
Where Flashblocks fits in Base's design
Flashblocks is one part of a broader effort across the OP Stack ecosystem to make rollups feel faster without weakening the security guarantees that come from settling to Ethereum. It went live on Base mainnet in mid 2025 and has been used by RPC providers and block builders serving the network since.
If you are curious about how Base processes transactions more broadly, from the sequencer that currently orders transactions to how blocks eventually settle on Ethereum, our articles on what a sequencer is and how Base stays secure through optimistic rollups cover the rest of that picture.
The takeaway
Flashblocks does not change what happens to your transaction. It changes how quickly you find out what happened. By breaking Base's 2 second block into roughly ten 200 millisecond updates, it gives wallets and apps a fast, reliable signal that your swap went through, well before the full block is sealed. For everyday swapping on Base, that mostly means one thing: less waiting, more certainty.