# Realtime FAQs

## Block Building and Availability

#### How often are Realtime blocks produced

* The realtime target interval is variable, but currently set to 100ms. A 12-second canonical block contains \~ 80 realtime sub-blocks (indexed from 0 to \~80) with the block building typically starting at T+4.&#x20;

#### Will the number of Realtime blocks per block always be the maximum?&#x20;

* Not always. Heavy execution in one interval may reduce time available for subsequent intervals. The REALTIME\_TIME setting is a target, not a strict guarantee

#### Do large gas transactions get delayed?&#x20;

* High gas transactions can be included in any realtime block with sufficient gas capacity. Placement is optimized by heuristics, but available gas decreases as transactions fill earlier realtime blocks.&#x20;

#### Why isn't the realtime block building always enabled?&#x20;

* Currently we run about 4% of Ethereum Validators through the marketplace. When the validator assigned to the current slot hasn't delegated to us, the realtime block building will be disabled.&#x20;

#### How do you sort each sub-block in real time?

* As we assemble every sub-block, we keep reordering simulated bundles/txs by their effective priority fee. So the highest-paying orders are always tried first at each sub-block.

#### How does the GWEI token change that ranking?

* If the sender holds GWEI token, we boost its simulated profit before ranking using a saturating curve:

$$
\text{boost%} = Y\_{\max}\left(1 - e^{-k \cdot B\_{\text{gwei}}}\right)
\text{multiplier} = 1 + \frac{\text{boost%}}{100}
$$

* Where B<sub>gwei</sub> is the holder’s balance expressed in GWEI. The boosted profit produces a higher effective priority fee, so the order moves up in the sub-block queue.

## High Availability and Safety

#### What happens if the realtime builder fails?&#x20;

* Our ETHGas relay will fallback to a regular MEV-Boost block build (including pre-confirmation bundles).&#x20;

#### Do Realtime blocks change the safety model of Ethereum?&#x20;

* No, each realtime block is validated by the same execution engine as normal blocks

#### Why do we need ETHGas realtime block building?&#x20;

* ETHGas realtime blocks change how fast apps can respond on Ethereum. Instead of waiting for full block finality (12 secs), you get an early signal of inclusion, fast enough to make things like trading, gaming, or live dashboards feel instant. It also works with standard RPC methods and doesn't require any new setup.&#x20;

#### How does ETHGas realtime block building prevent MEV attacks?&#x20;

* As realtime blocks build and finalize a new sub-block roughly over 50-100ms, this leaves limited time for a searcher to see your transaction in the mempool and then exploit it — 100ms sub-blocks are expected to have about 91% less MEV.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ethgas.com/overview/realtime/realtime-faqs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
