Private RPC Confirmation Time and Builder Inclusion
How long does a private RPC transaction take to confirm? Often one or a few 12-second slots; builder access and priority fee set the wait on Ethereum.
The Blockheight Editors··2 min read
A private RPC transaction often confirms in the next block or within a few blocks, but the wait depends on whether a builder that received it wins a slot and chooses to include it. Ethereum produces one slot every 12 seconds, so each missed slot adds about 12 seconds.
Take a swap sent through Flashbots Protect. The private RPC shares the signed transaction with a selected set of block builders, rather than broadcasting it to the public mempool. If a receiving builder wins the next slot and includes the swap, it confirms in about 12 seconds; otherwise, it can wait for a later slot.
What sets the wait?
- How many builders receive the transaction
- Whether one of them wins a slot
- The transaction’s priority fee
These factors determine how often the transaction has a chance to enter a block. A transaction reaches only the builders selected by its private RPC route, not every proposer or builder on Ethereum. Each slot creates another opportunity when a receiving builder wins.
The priority fee still matters on a private route. Builders rank transactions by the value they can earn from including them, and the priority fee contributes to that value. A low tip can leave a transaction behind better-paying transactions, extending its wait even when it has reached a winning builder.
Delay can also grow when fewer builders receive the transaction, because fewer winning blocks are produced by builders with access to it. And if a slot’s proposer does not use MEV-Boost, a transaction sent only to builders may have fewer paths into that block. The wait is therefore measured in 12-second slots, with the odds shaped by builder access and the fee.
Flashbots Protect and other private routes change who sees a transaction before inclusion. The broader topic of private transactions ethereum includes how those routes send transactions to builders rather than the public mempool.
For a fee estimate, consider both the priority fee and the share of blocks won by builders receiving the transaction. A stronger tip can improve its ranking, but the exact confirmation slot remains uncertain until a receiving builder wins and includes it.