Gas Auctions and Block Building: How Your Transaction Gets Included

Every Ethereum transaction enters an auction for blockspace. Here is who builds the block, how the auction is settled, and what determines your inclusion latency.

The path from your wallet's 'sign and submit' tap to your transaction landing on-chain is a sophisticated multi-party process: you submit to a node, the node propagates to the mempool, builders construct candidate blocks bidding for inclusion in the next slot, the proposer accepts the highest-paying bundle, and the validator publishes the block. Most users never see this layer, but it determines how fast and how cheaply your transactions confirm.

EIP-1559 Recap

• Base fee: an algorithmically-set per-gas price that adjusts each block to target 50% block fullness
• Priority fee (tip): an optional per-gas amount the user pays to the validator on top of the base fee
• Total cost: gas used × (base fee + priority fee) — base fee is burned, priority fee goes to validator
• Block fills greedily by total gas price — high tippers get included first
• Goal: smoother, more predictable gas pricing than the pre-1559 first-price auction

MEV-Boost and the Builder Layer

Since the Merge, Ethereum validators outsource block construction to specialised builders. A builder ingests the public mempool plus private order flow (Flashbots, MEV-Share, BloXroute) and constructs the most profitable block. The builder pays the validator a 'bid' for proposing the builder's block. The validator picks the highest bid via the MEV-Boost relay. This separation means the validator does not need to be sophisticated — they just sell their block-proposal rights to the builder market.

Where Your Transaction Actually Sits

• Public mempool: visible to all builders and all searchers — also visible to MEV bots
• Flashbots Protect: private submission, bundled by Flashbots, no exposure to public mempool
• MEV-Share: partial-disclosure mempool that lets searchers back-run but not front-run
• Builder-direct: large flow goes directly to one or more builders with custom inclusion guarantees
• Private-pool RPCs: most modern wallets and DEX aggregators submit through one of these by default

Inclusion Latency Math

• Public mempool, base-fee tip: typically 1-2 blocks (12-24 seconds) at low congestion
• Public mempool, generous tip: usually 1 block (12 seconds)
• Flashbots Protect: 1 block on average, occasional 2-3 block delays during builder competition
• Failed inclusion: if your tip is below the marginal price, your tx sits indefinitely until the base fee drops or you bump the tip
• L2 inclusion: 1-2 seconds on Arbitrum/Optimism/Base; <1 second on Solana

Practical Takeaways

For high-stakes trades, use a private-mempool RPC (most wallets including Steyble default to one) and set a tip that comfortably exceeds the current marginal builder bid. For low-stakes transfers, the base-fee tip is fine — your tx will land in 1-3 blocks. For multi-step DeFi transactions where partial execution is dangerous (e.g., a leveraged loop), prefer atomic-bundle inclusion through Flashbots so all legs land in the same block or none of them do.