> For the complete documentation index, see [llms.txt](https://l1x-sdk.gitbook.io/l1x-foundation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://l1x-sdk.gitbook.io/l1x-foundation/l1x-technology-explained/l1x-time-units.md).

# L1X Time Units

## Time Units <a href="#toc140645944" id="toc140645944"></a>

L1X blockchain employs a structured approach to time measurement, with slots as the smallest unit. One block is created within each slot, ensuring consistent and efficient processing of transactions. This section explores all four primary time units in the L1X blockchain as summarized in the table below.

| **Time Unit** | **Relative Units** | **Time** | **Blocks** |
| ------------- | ------------------ | -------- | ---------- |
| 1 Slot        | Base Unit          | 0.5 secs | 1 block    |
| 1 Chunk       | 40 slots           | 20 secs  | 40 blocks  |
| 1 Epoch       | 3 chunks           | 60 secs  | 120 blocks |
| 1 Cube        | 3 epochs           | 180 secs | 360 blocks |

&#x20;                                                            *Table 5 L1X Time Units*

## Slots <a href="#toc140645945" id="toc140645945"></a>

Slots represent the smallest time unit. Each slot has a fixed duration of 0.5 seconds. Within each slot, a single block is created, encapsulating a batch of validated transactions. The utilization of slots ensures a regular and predictable block creation schedule, contributing to the network's stability and transaction throughput.

## Chunks <a href="#toc140645946" id="toc140645946"></a>

To organize blocks within larger time intervals, the L1X blockchain introduces the concept of chunks. Each chunk consists of 40 slots, resulting in a 20-second time interval. By grouping blocks into chunks, the L1X blockchain enhances efficiency in block management and maintains a consistent rhythm for network operations.

## Epochs <a href="#toc140645947" id="toc140645947"></a>

The L1X blockchain further aggregates chunks into epochs. An epoch comprises three consecutive chunks, resulting in a 60-second time period or 1 minute. This larger time unit allows for a broader evaluation of network performance, consensus, and synchronization. Epochs provide a useful reference point for analyzing blockchain metrics and facilitating various network operations.

## Cubes <a href="#toc140645948" id="toc140645948"></a>

Cubes represent an extended time unit within the L1X blockchain. Each cube consists of three consecutive epochs, resulting in a time period of 3 minutes. The use of cubes enables long-term analysis, trend identification, and strategic planning within the blockchain network. Cubes serve as key milestones for tracking the progression of the L1X blockchain's performance and growth.

By implementing slots, chunks, epochs, and cubes, the L1X blockchain optimizes time management, ensuring precise block creation, consistency, and effective network operation. This systematic approach to time units enhances the blockchain's scalability, performance, and overall operational efficiency.


---

# 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://l1x-sdk.gitbook.io/l1x-foundation/l1x-technology-explained/l1x-time-units.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.