> For the complete documentation index, see [llms.txt](https://zokyo-auditing-tutorials.gitbook.io/zokyo-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zokyo-auditing-tutorials.gitbook.io/zokyo-tutorials/tutorial-30-inconsistent-block-lengths-across-chains.md).

# Tutorial 30: Inconsistent block lengths across chains

{% hint style="info" %}
[**Book an audit with Zokyo**](https://www.zokyo.io/)
{% endhint %}

#### Introduction to Block Number and Block Timestamp

In blockchain systems, two important metrics are frequently used to measure the passage of time and the progression of transactions: `block.number` and `block.timestamp`.

* **`block.number`** refers to the current number of blocks mined since the creation of the blockchain, essentially marking the block's sequential position. It provides a measure of the network's progression by counting how many blocks have been added since the genesis block.
* **`block.timestamp`** is a Unix timestamp that indicates when a specific block was mined. It gives the real-world time, in seconds, at which the block was created.

For Ethereum, it is generally assumed that a new block is produced roughly every **12 seconds**, a metric often used in smart contract development. However, this block time can vary, and making incorrect assumptions about it can result in serious vulnerabilities. Furthermore, the use of `block.number` and `block.timestamp` can vary across different EVM-compatible chains, making hardcoding block assumptions even more dangerous in multi-chain deployments.


---

# 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://zokyo-auditing-tutorials.gitbook.io/zokyo-tutorials/tutorial-30-inconsistent-block-lengths-across-chains.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.