> For the complete documentation index, see [llms.txt](https://userguide.cryptoquant.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.cryptoquant.com/cryptoquant-metrics/utxo/profit-and-loss-utxo.md).

# Profit and Loss (UTxO)

The number of UTxOs being in profit or loss by comparing the price between created and destroyed

## Definition

Profit and Loss (UTxO) evaluates the number of UTxOs being in profit or loss by comparing the price between created and destroyed. When the price at destroyed time is higher than created, this transaction is in profit.

$$
\text{UTxOs in Profit} = \text{Number of UTxOs being in profit}
$$

$$
\text{UTxOs in Loss} = \text{Number of UTxOs being in loss}
$$

$$
\text{Percent UTxOs in Profit} = 100 \* \frac{\text{UTxOs in Profit}}{\text{Number of UTxOs}}
$$

$$
\text{Percent UTxOs in Loss} = 100 \* \frac{\text{UTxOs in Loss}}{\text{Number of UTxOs}}
$$

## Interpretation

Assuming that UTxO's movement is the result of trading transaction, Profit and Loss (UTxO) is the basic data that shows how many UTxOs are in loss.

### By Examining Absolute Numbers <a href="#interpretation" id="interpretation"></a>

If you want to look for how **many** UTxOs are in profit/Loss&#x20;

* **Numbers** of UTxOs that are in **Profit**: [Profit amount](https://cryptoquant.com/overview/btc-network-indicator/16432?window=day)

  Profit amount naturally shows a correlation to the price
* **Numbers** of UTxOs that are in **Loss**: [Loss Amount](https://cryptoquant.com/overview/btc-network-indicator/16433?window=day)

  Loss amount naturally shows an inverse correlation to the price

### By Examining Ratio <a href="#indicating-selling-or-buying-pressure" id="indicating-selling-or-buying-pressure"></a>

If you want to look for ratio of UTxOs are in profit/Loss comparative to all UTxOs

* **Ratio** of UTxOs that are in **Profit:** [Profit percent](https://cryptoquant.com/overview/btc-network-indicator/16434?window=day)

  Profit percent naturally shows a correlation to the price
* **Ratio** of UTxOs that are in **Loss:** [Loss percent ](https://cryptoquant.com/overview/btc-network-indicator/16435?window=day)

  Loss percent naturally shows an inverse correlation to the price

## Link to Our Data

* [BTC: Profit Amount (UTxO) Live Chart](https://cryptoquant.com/overview/full/16432?window=day)
* [BTC: Loss Amount (UTxO) Live Chart](https://cryptoquant.com/overview/full/16433?window=day)
* [BTC: Profit Percent (UTxO) Live Chart](https://cryptoquant.com/overview/full/16434?window=day)
* [BTC: Loss Amount (UTxO) Live Chart](https://cryptoquant.com/overview/full/16435?window=day)


---

# 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://userguide.cryptoquant.com/cryptoquant-metrics/utxo/profit-and-loss-utxo.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.