> 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/realtime.md). # Realtime Execution ETHGas Realtime Execution is the new block-building method that accelerates Ethereum's user experience up to 240x. This enables all users and dapps to benefit from preconfirmations or synthetic block times as fast as 50ms without compromising security guarantees. The Realtime Builder streams pre-confirmations, or preliminary state updates continuously before the next block is finalized providing a seamless user experience for all users and dapps, alongside an economic guarantee to support the broadcasted state. This is built for developers who need a blazingly fast UX from: * Payments: Instant payment confirmations * DeFi: Swap multiple times within a block with positions that update immediately * Marketplaces: Fast and Frictionless * Trading: Prevent frontrunning and delivery real-time price updates. {% embed url="" %} ## Background & How it Works Ethereum blocks are produced every 12 seconds and for years this had been taken as largely immutable. Every new L1 and L2 blockchain's key value proposition has been "we are faster" — and with ETHGas Realtime, that is no longer the case. ETHGas breaks these blocks into hundreds of intervals so instead of waiting for the full block time to execute all transactions, the execution client continuously creates and broadcasts the current state every 50-100 milliseconds. Each realtime block includes all transactions processed so far, along with updated balances and contract states. Apps can query this using the ETHGas realtime RPC or othe rfuture RPC providers that integrate us and deliver the speed their end users expect. --- # 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/realtime.md?ask=&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.