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

# Transactions

/blockchain-v2/{asset}/transactions

Transactions, just like double entry accounting transactions, are groups of balance updates that are ordered within a block. The **Transactions** endpoint returns a list of accounts, which have the following fields:

| Field                      | Description                                                                                                                                                                                                                                                           |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| txid                       | Identifier of the transaction                                                                                                                                                                                                                                         |
| block\_hash                | Hash of the block containing the transaction                                                                                                                                                                                                                          |
| height                     | Height of the block containing the transaction                                                                                                                                                                                                                        |
| tx\_position               | Position of the transaction within a block                                                                                                                                                                                                                            |
| consensus\_time            | [Consensus timestamp](/network-data/atlas-overview.md#consensus-timestamp); always increases monotonically                                                                                                                                                            |
| min\_chain sequence number | Starting [sequence number](/network-data/atlas-overview.md#chain-sequencing) (global ordering of the first update in this transaction relative to all other updates recorded on the ledger up until that point) for the balance updates occurring in this transaction |
| max\_chain sequence number | Last [sequence number ](/network-data/atlas-overview.md#chain-sequencing)(global ordering of the last update in this transaction relative to all other updates recorded on the ledger up until that point) for the balance updates occurring in this transaction      |
| n\_balance updates         | Number of balance updates                                                                                                                                                                                                                                             |
| amount                     | Amount of the balance updates                                                                                                                                                                                                                                         |
| stale                      | Indicator if the block is stale.                                                                                                                                                                                                                                      |
| version                    | Version of the transaction                                                                                                                                                                                                                                            |
| physical\_size             | Physical size of the transaction (bytes)                                                                                                                                                                                                                              |
| consensus\_size            | Consensus size of the transaction                                                                                                                                                                                                                                     |
| Fee                        | Fee of the transaction                                                                                                                                                                                                                                                |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gitbook-docs.coinmetrics.io/network-data/atlas-overview/transactions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
