1month
)1w
)24h
)1h
)10m
)24h
resolution shows the total number of active addresses over 24 hours (the time window). In addition, a new data point is provided once a day (the frequency). The same mechanism is applied analogously to all other resolutions.24h
resolution. Whether other resolutions are available for a particular metric, depends on the metric and your plan. For a full overview of which metric is currently avaiable a what resolution, please refer to our Metrics Catalogue.UTC
and always refer to the start of an interval.2019-05-01
--> Includes data from2019-05-01 00:00 UTC
to 2019-05-31 23:59 UTC
(i.e. May 2019)2019-05-13
--> Includes data from 2019-05-13 00:00 UTC
to 2019-05-19 23:59 UTC
(i.e. Week 20)2019-05-13
--> Includes data from2019-05-13 00:00 UTC
to 2019-05-13 23:59 UTC
2019-05-13 10:00 UTC
--> Includes data from2019-05-13 10:00 UTC
to 2019-05-13 10:59 UTC
2019-05-13 10:20 UTC
--> Includes data from 2019-05-13 10:20 UTC
to 2019-05-13 10:29 UTC
2:30 UTC
2:30 UTC
00:00 UTC
to 3:00 UTC
(e.g. 00:00
, 00:10
, 00:20
, ..., 3:00
):00
(e.g. 9:00
, 10:00
, 11:00
, ...)09:00
, 09:10
, 09:20
, 09:30
, ...)1d
resolution:00:00 UTC
the metric updater will be triggered in order to create the last day's datapoint. Because we wait for a 1 block confirmation before the data of that block is included in the computation of the metric, at this moment there might be still a block missing for that last interval (the previous day in this case). In the next metric updater execution (in case of daily metrics that's 10 minutes later, see above) that last block (if confirmed by a subsequent block) will be finally included into the last datapoint and therefore the value of that last datapoint might slightly change. Depending on the block interval, the latest datapoint might also be only updated and complete at later metric updater executions.