> For the complete documentation index, see [llms.txt](https://docs-old.zus.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-old.zus.network/concepts/architecture/mining-on-the-zues-blockchain/block-finalization.md).

# Block Finalization

After a miner notarizes a block, it attempts to determine which blocks are finalized; after a block is considered finalized, a miner will not accept any alternate blocks to this block or earlier blocks.

The miner begins at the most recently produced block and walks back through the previous block to check for notarizations. If a block has received notarization from more than two-thirds of the mining network, it is marked as final; by extension, so are all previous blocks in that blockchain.

Figure 1 below shows the block notarization and finalization process.

![Figure 1 :Block Notarization and Finalization](https://user-images.githubusercontent.com/65766301/128001961-e0e99cd9-c574-4356-a31b-623edd458130.jpg)

Each row represents the precedence of blocks, with the top row representing the block produced by the highest priority miner for the round. Each column represents the round number.

Each node represents a single block. Yellow blocks are notarized, but not yet finalized; green blocks have been finalized; and grey blocks have been produced 3 but neither notarized nor finalized. The notation “R57,9,M4” indicates that the block was produced in round 57, that it has 9 notarizations, and that it was produced by miner 4.

The figure shows that in round 61, miner 3’s block failed to get sufficient verification, and the second highest priority block was notarized and finalized in its place. In round 63, the highest priority block producer failed to make a block; therefore, the second highest priority block was again notarized and finalized in its place


---

# 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://docs-old.zus.network/concepts/architecture/mining-on-the-zues-blockchain/block-finalization.md?ask=<question>&goal=<endgoal>
```

`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.