Glassnode Docs
WebsiteStudioInsightsTwitter
  • Welcome to Glassnode
    • Introduction
      • Studio
  • 📊Data
    • General Information
      • Timestamps and Resolutions
      • Data Availability
      • Data Finalization
    • Metric Catalog
    • Supported Blockchains
    • Supported Assets
      • Market Metrics Coverage
      • On-chain Metrics Coverage
    • Point-in-Time Metrics
  • 📖Guides & Tutorials
    • Getting Started
      • Use-Case Tutorials
        • Tutorial 1 - Navigating Market Tops and Bottoms
        • Tutorial 2 - Introduction to On-chain Activity
        • Tutorial 3 - Fundamentals of Proof-of-Work Mining
        • Tutorial 4 - Introduction to Supply Dynamics
      • Get started with Glassnode Metrics
      • Granular Cohorts for Key On-Chain Metrics
    • Metric Guides
      • Market Capitalization
      • Realized Capitalization
      • MVRV
        • LTH-MVRV
        • MVRV Ratio
        • MVRV-Z Score
        • STH-MVRV
      • SOPR
        • SOPR (Spent Output Profit Ratio)
        • aSOPR (Adjusted SOPR)
        • LTH-SOPR
        • STH-SOPR
      • Unrealized Profit/Loss
        • NUPL (Net Unrealized Profit/Loss)
        • Unrealized Profit
        • Unrealized Loss
        • LTH-NUPL
        • STH-NUPL
      • Realized Profit/Loss
        • Net Realized Profit/Loss
        • Realized Profit
        • Realized Loss
      • Coin Issuance
        • Puell Multiple
      • Stablecoin
        • SSR (Stablecoin Supply Ratio)
      • Coin Days Destroyed
        • CDD (Coin Days Destroyed)
        • Supply-Adjusted CDD
        • Binary CDD
        • CYD (Coin Years Destroyed)
        • Supply-Adjusted CYD
        • Reserve Risk
      • Liveliness
      • Dormancy
        • Average Coin Dormancy
        • Supply-Adjusted Dormancy
      • Lifespan
        • Spent Output Age Bands (SOAB)
        • Average Spent Output Lifespan (ASOL)
        • Median Spent Output Lifespan (MSOL)
      • NVT
        • NVT Ratio
        • NVT Signal
        • Velocity
      • Stock to Flow
        • Stock to Flow Ratio
        • Stock to Flow Deflection
      • Price Distribution
        • URPD (UTXO Realized Price Distribution)
        • SOPD (Spent Output Price Distribution)
      • Accumulation Trend Score
      • Long and Short-Term Holder Supply
        • Supply Held by Long and Short-Term Holders
      • Profit/Loss (Supply)
        • Percent Supply in Profit
        • Supply in Profit
        • Supply in Loss
      • Age Distribution
        • HODL Waves
        • Realized Cap HODL Waves
      • Profit/Loss (UTXO)
        • Percent UTXOs in Profit
        • UTXOs in Profit
        • UTXOs in Loss
    • On-Chain Concepts
      • Entity-Adjusted Metrics
      • On-chain Glossary
      • Understanding UTXOs - The Gold Coin Analogy
      • UTXO vs. Account-Based Chains
    • Workbench Guide
  • ⚙️API
    • Introduction
    • API Key
    • API Credits
    • Metadata
    • Bulk metrics (beta)
    • Endpoints
      • Addresses
      • Bridges
      • Blockchain
      • Breakdowns
      • DeFi
      • Derivatives
      • Distribution
      • Entities
      • ETH 2.0
      • Fees
      • Indicators
      • Institutions
      • Lightning
      • Market
      • Mempool
      • Mining
      • Point-In-Time
      • Protocols
      • Signals
      • Supply
      • Transactions
  • ℹ️Further Information
    • Changelog
      • 2025
      • 2024
      • 2023
      • 2022
      • 2021
      • 2020
    • Support FAQ
    • Affiliate FAQs
    • Exchange Data: Transparency Notice
Powered by GitBook
On this page
  1. Data
  2. General Information

Data Finalization

The latest released datapoint can be subject to change.

Before a block is included into the computation of a metric we wait until a block is confirmed:

  • BTC: 1 block confirmation

  • ETH + ERC20 Tokens: 12 blocks confirmation

The reason to wait for block confirmations is to reduce the amount of data changes, e.g. by reducing the probability of initial inclusion of orphan blocks.

Nonetheless, waiting for block confirmations leads to the fact that not always all blocks relevant to the last interval are included, and therefore the computation of the last datapoint of a metric can be initially incomplete.

Example for a Bitcoin metric at a 1d resolution:

At 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) 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.

Sidenote:

  • BTC does not enforce monotonic timestamp sequences (e.g. block #10 can have a timestamp that is earlier than the timestamp of block #9). This happens only very rarely, but it means that there is a possibility that a new block is added to the blockchain with a timestamp that is earlier than the last block. If this happens, the datapoint of the interval where this timestamp resides in, will change.

  • We are in the process of updating our docs with the latest released datapoints for newly supported blockchains

PreviousData AvailabilityNextMetric Catalog

Last updated 1 month ago

📊