> For the complete documentation index, see [llms.txt](https://docs.ethgas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ethgas.com/overview/which-blocks-are-realtime.md).

# Which Blocks are Realtime?

### Realtime Markets API

{% tabs %}
{% tab title="Mainnet" %}
<https://prod-mainnet.ethgas.com/api/v1/p/realtime/markets>
{% endtab %}

{% tab title="Hoodi" %}
<https://prod-hoodi.ethgas.com/api/v1/p/realtime/markets>
{% endtab %}
{% endtabs %}

API Documentation: [https://developers.ethgas.com/#realtime-markets](https://developers.ethgas.com/?http#realtime-markets)

ETHGas Realtime slots only occur when registered validators propose blocks. This means that not all slots are available for faster blocks. The Realtime Markets API can be used to return an array of all upcoming Realtime slots in the current and next epoch.

<figure><img src="https://1913553586-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBk99eVkZsNrI6feXAyYs%2Fuploads%2FhM4mR81drrC8RZ6t6HhV%2Fimage.png?alt=media&amp;token=9c2bfa50-0fc7-4dab-9d67-cac15e48a4a2" alt=""><figcaption></figcaption></figure>

Sub-slots are sequenced with a target timing of 200ms and require a 3-4 second window at the start of the block before the fast sequencing starts. This is due to the time it takes for the previous block's state to update/propagate.&#x20;

Where there are two consecutive realtime (12-sec) blocks, the 200ms sub-slot sequencing happens continuously between the two blocks for a seamless experience.&#x20;

### Example Responses

{% code title="Example response with Realtime slots in the lookahead" overflow="wrap" %}

```json
{
    "success": true,
    "data": {
        "slots": [
            14000000,
            14000001
        ]
    }
}
```

{% endcode %}

{% code title="Example response without Realtime slots in the lookahead" overflow="wrap" %}

```json
{
    "success": true,
    "data": {
        "slots": []
    }
}
```

{% endcode %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ethgas.com/overview/which-blocks-are-realtime.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
