> For the complete documentation index, see [llms.txt](https://doc.tryethernal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.tryethernal.com/dashboard-pages/blocks.md). # Blocks ## Index The [/blocks](https://app.tryethernal.com/blocks) page will display all synchronized blocks, with basic details such as mining timestamp or the number of transactions.\ Block numbers link to the block details page\ If a block is mined but the CLI is not listening, the block won't appear here. ### Details Each block has its own page, with the URL following the pattern `/block/${blockNumber}`. Transactions contained in this block are all displayed.\ If a transaction is a contract call and artifacts have been uploaded, clicking on it will decode the data.\ You'll be able to see: * Function call signature with the parameters * Emitted events * Watched variables data The watched variables data will be the one watched for the contract called in the transaction. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://doc.tryethernal.com/dashboard-pages/blocks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.