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

# 평균 코인 생존 기간 (Mean Coin Age)

블록체인 상에 존재하는 전체 코인의 평균 생존 기간을 나타냅니다

## 정의

블록체인 상에 존재하는 전체 코인의 평균 생존 기간을 나타냅니다

$$
평균 코인 생존 기간 (Mean Coin Age)=\frac{\sum\_{u \in \text{unspent outputs}}\text{나이}\_u\*\text{개수}*u}{\sum*{u \in \text{unspent outputs}}\text{개수}\_u}
$$

## **해석**

평균 코인 생존 기간은 CDD와 유사하지만 UTXO의 나이에 더욱더 치중합니다.

평균 코인 생존 기간 (달러)는 MCA 지표를 코인이 마지막으로 거래된 시점의 가격 (USD)으로 가중하여 계산한 지표입니다.

## 크립토퀀트 데이터 링크

* [비트코인 : 실시간 평균 코인 생존 기간 차트](https://cryptoquant.com/overview/btc-network-indicator/16573?window=day)
* [비트코인 : 실시간 평균 코인 생존 기간 (달러) 차트](https://cryptoquant.com/overview/btc-network-indicator/16574)


---

# 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/ko/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 `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.