> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/higher-learning/bsv-academy/deep-dive-in-bsv-blockchain/utxo-model-unlock-transaction-efficiency-and-privacy/utxo-model-overview.md).
# UTXO Model Overview
### Transaction Processing
The **UTXO (Unspent Transaction Output)** model is foundational to the BSV blockchain, enabling an approach to **transaction processing** following the original Bitcoin protocol.
* Each UTXO acts like an **individual coin or bill**, allowing for independent spending.
* This model supports **parallelized transaction processing**, akin to digital cash, where multiple transactions can occur simultaneously without conflicts.
* Transactions are validated based on the **consumption of UTXOs**, ensuring that each transaction is **atomic**—either fully valid or entirely rejected.
### Inputs and Outputs
Every transaction in the UTXO model consists of **inputs and outputs**, which are essential for transferring ownership of funds.
* **Inputs**: Each input references a previous UTXO and includes an **unlocking condition**, allowing the specified UTXO to be spent.
* **Outputs**: Each output defines a **value** and a **locking condition**, securing the tokens for the new owner.
* A transaction is structured with a **version number**, a list of inputs, a list of outputs, and a **lock time value**, which facilitates non-final transactions and payment channels.
* Outputs that remain unspent become new UTXOs, available for **future transactions**.
---
# 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://hub.bsvblockchain.org/higher-learning/bsv-academy/deep-dive-in-bsv-blockchain/utxo-model-unlock-transaction-efficiency-and-privacy/utxo-model-overview.md?ask=&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.
