> For the complete documentation index, see [llms.txt](https://docs.ramestta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ramestta.com/blockchain-fundamental/introduction.md).
# Introduction
A block in a blockchain is a group or collection of information. The information is added to the block in a blockchain, by connecting it with other blocks in the chronological order and creating a chain of blocks linked together. Let’s take the example of Google spreadsheet or MS Excel (Windows). This spreadsheet is shared among different computer networks, where everyone has a copy. The spreadsheet contains data and information of transactions made by individuals. Anyone with a copy can access that spreadsheet but no one can edit or change it. This is how the blockchain works. It uses blocks, whereas spreadsheet works with “rows” and “columns”.
The blockchain is a *distributed ledger.* This means that a ledger is spread across the network between all peers in the network, and each peer holds a copy of the complete ledger. Some key properties that make blockchain far superior and better than the traditional system of information ledgering.
---
# 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.ramestta.com/blockchain-fundamental/introduction.md?ask=&goal=
```
`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.