> 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/mean-coin-age-mca.md).

# Mean Coin Age (MCA)

Mean Coin Age is the mean value of products of coins unspent transaction output alive days and its value.

## Definition

Mean Coin Age(MCA) is the mean value of products of coin unspent transaction output (UTxO) alive days and its value.

$$
MCA=\frac{\sum\_{u \in \text{unspent outputs}}\text{lifespan}\_u\*\text{value}*u}{\sum*{u \in \text{unspent outputs}}\text{value}\_u}
$$

## Interpretation

MCA is similar to CDD but focuses more on unspent transaction output. Mean Coin Dollar Age is the sum value of products of coin unspent transaction output alive days, value, and the price at the created time.  This indicator enables estimating the Long-Term Holders' portion.

* Mean Coin Age(MCA): MCA is the average age of UTxO. MCA drop implies the massive move of Bitcoin UTxOs that haven't moved for a long time.
* Mean Coin Dollar Age(MCDA): MCDA is an indicator weighted by UTxO created price(USD) to the MCA.

## Link to Our Data

* [BTC: Mean Coin Age Live Chart](https://cryptoquant.com/overview/full/16573?window=day)
* [BTC: Mean Coin Dollar Age Live Chart](https://cryptoquant.com/overview/full/16574?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 dynamically 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/mean-coin-age-mca.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 `build a script that syncs our docs to a CMS` 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.