# Resolutions All metric data in our system is reported in **UTC** time and always refers to the **start of an interval**. The resolution of a metric determines both the frequency at which it is updated and the time window over which the data is aggregated or calculated. **Daily Resolution (1d)** * Example: `2025-01-22 (00:00 UTC)` * Includes data from: `2025-01-22 00:00 UTC` to `2025-01-22 23:59 UTC` **Weekly Resolution (1W)** * Example: `2025-01-20 (00:00 UTC)` * Includes data from: `2025-01-20 00:00` UTC to `2025-01-26 23:59 UTC` (i.e., Week 4) **Monthly Resolution (1M)** * Example: `2025-01-01 (00:00 UTC)` * Includes data from: `2025-01-01 00:00 UTC` to `2025-01-31 23:59 UTC` (i.e., January 2025) **Resolution** refers to: 1. **The frequency at which data is updated**: How often new data points are recorded. 2. **The time window over which data is aggregated**: The span of time that a metric's value represents. For example: * The number of active addresses with a **daily resolution** shows the total number of active addresses over the 24-hour time window. A new data point is provided once a day. * Similarly, a metric with a **weekly resolution** aggregates the data over a 7-day time window and provides a new data point once per week. This same mechanism is applied analogously to all other resolutions. Some metrics, such as the number of addresses with a non-zero balance, reflect the **current state of the blockchain** rather than an aggregate over a time window. For such metrics: * **The value refers to the state at the end of the interval**. * Example: A daily metric for non-zero balance addresses reported for `2025-01-22` refers to the state of the blockchain at `2025-01-22 23:59 UTC`. --- # Agent Instructions: 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 current page URL with the `ask` query parameter: ``` GET https://docs.icterminal.com/metrics/resolutions.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.