# Block structure & serialization

A zkopru block is submitted to the layer1 in a serialized form. Then, the checksum of the proposal becomes the proposal ID and is used for the challenge system.

## Block structure

The zkopru block includes a header and a body.

![Block details](/files/-MBY98CR5Eta1cyRQTbu)

Edit diagram here

## Header

The first 340 bytes of the data should be the block header. The block header contains the following data:

| Property                            | type    |
| ----------------------------------- | ------- |
| Proposer's address                  | address |
| Parent block hash                   | bytes32 |
| Fee                                 | uint256 |
| Latest UTXO tree's root             | uint256 |
| Latest UTXO tree's leaf index       | uint256 |
| Nullifier tree's root               | bytes32 |
| Latest withdrawal tree's root       | uint256 |
| Latest withdrawal tree's leaf index | uint256 |
| Transactions' root                  | bytes32 |
| Deposits' root                      | bytes32 |
| Migrations' root                    | bytes32 |

## Body

A block body consists of transactions, mass deposits, and mass migrations. Moreover, the block header should contain correct information from the body. If the header does not have the correct value, the proposer will get slashed through the challenge system.

### Transactions

![Tx serialization](/files/-MBcikJp6pZDYJ2XrVjw)

### Mass deposits

![](/files/-MBciqV9Y1e0u71yjYfo)

### Mass migrations

![](/files/-MBcixTcJHqkEHWu-wsM)


---

# 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.zkopru.network/how-it-works/block.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.