> 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/es/utxo-data-indicators/dias-de-monedas-destruidas-cdd-binario.md).

# Días de Monedas Destruidas CDD Binario

El CDD binario es un valor y si la Oferta Ajustada de Días de Monedas Destruidas (Oferta Ajustada CDD) es mayor que la media de la Oferta Ajustada CDD, los Dias de Monedas Binaria apuntan a 1 y a 0

## Definición

Días de monedas destruidas binario es un valor binario y, si la Oferta Ajustada de Días de Monedas Destruidas son mayores que la Media de Oferta Ajustada de Días de Monedas Destruidas, los días de monedas binarios apuntan a "1" y apuntan a "0" en caso contrario

* **muestra 1:** Si la medida de la Oferta Ajustada CDD es mayor que el promedio de la Oferta Ajustada de CDD
* **muestra 0:** Si la medida de la Oferta Ajustada CDD es menor que el promedio de la Oferta Ajustada de CDD

## Interpretación

Muestra si los movimientos de los titulares a largo plazo son superiores o inferiores a la media. 

* La **alta densidad** de valor señala "1": Los titulares a largo plazo han movido sus monedas para una posible venta
* Una **Densidad baja** del valor que apunta a "1": los titulares a largo plazo no mueven sus monedas


---

# 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/es/utxo-data-indicators/dias-de-monedas-destruidas-cdd-binario.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.