> For the complete documentation index, see [llms.txt](https://docs.dh3.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dh3.io/specs/data-streams/streams.md).

# Streams

### Overview

The fundamental structure of our data handling system consists of raw block streams, transaction streams, and account streams to be added soon. Each component is meticulously designed to optimize data retrieval and ensure efficient resource utilization.

#### Blocks

Raw block streams serve as the bedrock for our data architecture. Blocks are organized in approximately 256MB batches. This organization facilitates targeted data retrieval by segregating data into yearly, monthly, and daily segments, thereby optimizing read operations and minimizing input/output resource strain.

#### Transactions

Our transaction streams evolve from the raw block streams and are categorized into numerous channels. This segregation helps in isolating specific data types, such as oracles, transactions with incomplete states, and others, to reduce false matches and increase rescan speeds during data extraction. As our system evolves, we anticipate the introduction of additional channels to address specific data retrieval needs with precision. Check out [channels](/specs/data-streams/channels.md) for details.

#### Accounts

In development...


---

# 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:

```
GET https://docs.dh3.io/specs/data-streams/streams.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.