Point-In-Time

Accumulation Addresses

get

The number of unique accumulation addresses. Accumulation addresses are defined as addresses that have at least 2 incoming non-dust transfers and have never spent funds. Exchange addresses and addresses receiving from coinbase transactions (miner addresses) are discarded. To account for lost coins, addresses that were last active more than 7 years ago are omitted as well.\n\nThis is the Point-in-Time (PiT) variant of Accumulation Addresses. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/addresses/accumulation_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/addresses/accumulation_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 810134
  }
]

Accumulation Balance

get

The total amount of funds held in accumulation addresses. Accumulation addresses are defined as addresses that have at least 2 incoming non-dust transfers and have never spent funds. Exchange addresses and addresses receiving from coinbase transactions (miner addresses) are discarded. To account for lost coins, addresses that were last active more than 7 years ago are omitted as well.\n\nThis is the Point-in-Time (PiT) variant of Accumulation Balance. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/addresses/accumulation_balance_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/addresses/accumulation_balance_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 2529988.80215483
  }
]

Accumulation Trend Score

get

The Accumulation Trend Score is an indicator that reflects the relative size of entities that are actively accumulating coins on-chain in terms of their BTC holdings. The scale of the Accumulation Trend Score represents both the size of the entities balance (their participation score), and the amount of new coins they have acquired/sold over the last month (their balance change score). An Accumulation Trend Score of closer to 1 indicates that on aggregate, larger entities (or a big part of the network) are accumulating, and a value closer to 0 indicates they are distributing or not accumulating. This provides insight into the balance size of market participants, and their accumulation behavior over the last month. For more information see the metric description in Glassnode Academy.\n\nThis is the Point-in-Time (PiT) variant of Accumulation Trend Score. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/accumulation_trend_score_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/accumulation_trend_score_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "price": 63192.37533942145,
      "score": 0.17004755552140915
    }
  }
]

Active Entities

get

The number of unique entities that were active either as a sender or receiver. Entities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Active Entities. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/active_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/active_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 230462
  }
]

Asia Year-over-Year Supply Change

get

\nThis metric aims at giving an estimate for the year-over-year change in the share of the Bitcoin supply to be held/traded in Asia.\n\nGeolocation of Bitcoin supply is performed probabilistically at the entity level. The timestamps of all transactions created by an entity are correlated with the working hours of different geographical regions to determine the probabilities for each entity being located in the US, Europe, or Asia. Working hours are defined as:\n\n* US: 8am to 8pm Eastern Time (13:00-01:00 UTC)\n* EU: 8am to 8pm Central European Time (07:00-19:00 UTC)\n* Asia: 8am to 8pm China Standard Time (00:00-12:00 UTC)\n\nAn entity's balance will only contribute to the supply in the respective region if the location can be determined with a high certainty. Supply held on exchanges wallets are excluded.\n \n\nThis is the Point-in-Time (PiT) variant of Asia Year-over-Year Supply Change. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/apac_1y_supply_change_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/apac_1y_supply_change_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.07187969162367636
  }
]

Bridges Deposits By Chain

get

This metric measures the USD value which is deposited into bridge smart contracts on Ethereum, and is therefore flowing out of the Ethereum blockchain, and into target blockchains. Deposit Volume is computed daily by multiplying the number of tokens deposited into bridges by the latest daily price of each token.\n\nBridges are protocols that enable digital assets to be transferred from one blockchain to another. When an asset is transferred out of Ethereum, it gets deposited and locked into a bridge smart contract. When the asset is transferred back to Ethereum, it is withdrawn and released from the smart contract.\n\nThis metric only includes bridge contracts on the Ethereum side. The bridges included in this metric cover bridge deposits into both L1 and L2 blockchains, providing information on the value transferred to both L1 competitors, and L2 scaling solutions. Each bridge included in this metric represents a single blockchain, except the ones labeled as multichain. That label is used to represent bridges that allow transferring assets across multiple different chains. \n\nThis is the Point-in-Time (PiT) variant of Bridges Deposits By Chain. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/bridges/deposits_by_chain_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/bridges/deposits_by_chain_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "arbitrum": 6355452.3741127085,
      "avalanche": 160312.67401539942,
      "aztec": null,
      "boba": null,
      "bsc": null,
      "deversifi": 62623.906856644746,
      "dydx": 80427.08846201803,
      "fantom": null,
      "fuse": null,
      "gluon_network": null,
      "gnosis_chain": 1644360.1157613294,
      "harmony": null,
      "heco_chain": null,
      "huobi": null,
      "immutable_x": 0,
      "layer2finance": null,
      "loopring": 3730.17,
      "moonriver": null,
      "multichain": 21883821.206434973,
      "near": 0.19008451,
      "optimism": 434428.2891749692,
      "polygon": 1225459.0307207252,
      "ronin": null,
      "rsk": 78929.658178,
      "secret_network": null,
      "solana": null,
      "sorare": 0,
      "zkswap": null,
      "zksync": 0
    }
  }
]

Bridges Net Flow By Chain

get

This metric shows the net USD value flowing into, or out of Ethereum bridge smart contracts, calculated as bridge deposits minus bridge withdrawals. It can also be considered to represent the net USD value flowing in, or out of the Ethereum blockchain via bridges. A positive value means that there is more value being deposited into bridges, which translates into a net value outflow from Ethereum. On the other hand, a negative value means that there is more USD value being withdrawn from bridges, which translates into more USD value flowing back into Ethereum.\n\nBridges are protocols that enable digital assets to be transferred from one blockchain to another. When an asset is transferred out of Ethereum, it gets deposited and locked into a bridge smart contract. When the asset is transferred back to Ethereum, it is withdrawn and released from the smart contract.\n\nThis metric only includes bridge contracts on the Ethereum side. The bridges included in this metric cover bridge deposits into both L1 and L2 blockchains, providing information on the value transferred to both L1 competitors, and L2 scaling solutions. Each bridge included in this metric represents a single blockchain, except the ones labeled as multichain. That label is used to represent bridges that allow transferring assets across multiple different chains.\n\nThis is the Point-in-Time (PiT) variant of Bridges Net Flow By Chain. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/bridges/net_volume_by_chain_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/bridges/net_volume_by_chain_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "arbitrum": 12844068.59427538,
      "avalanche": -481780.26777238376,
      "aztec": null,
      "boba": null,
      "bsc": null,
      "deversifi": -539002.8087753147,
      "dydx": -546650.664252042,
      "fantom": null,
      "fuse": null,
      "gluon_network": null,
      "gnosis_chain": 1322205.9863117326,
      "harmony": null,
      "heco_chain": null,
      "huobi": null,
      "immutable_x": -1720.7876758415528,
      "layer2finance": null,
      "loopring": 107363.02082925306,
      "moonriver": null,
      "multichain": 13978582.604653489,
      "near": -0.28322349495800003,
      "optimism": 120121.16411281636,
      "polygon": -49380754.32035558,
      "ronin": null,
      "rsk": 78929.658178,
      "secret_network": null,
      "solana": null,
      "sorare": 42164.973681973664,
      "zkswap": null,
      "zksync": -14150.504184829539
    }
  }
]

Bridges Transactions (Absolute)

get

The number of transactions (transaction count) in the Ethereum network by contracts that allow transfer of tokens between different blockchains.\n\nThis is the Point-in-Time (PiT) variant of Bridges Transactions (Absolute). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_count_bridges_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_count_bridges_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "arbitrum": 997,
      "axie_infinity": null,
      "hop": null,
      "immutable_x": 178,
      "multichain": 1,
      "optimism": 51,
      "other_bridges": 2006,
      "polygon": 267,
      "synapse": 35,
      "wormhole": 479,
      "zksync": 18
    }
  }
]

Bridges Transactions (Relative)

get

The relative amount (share) of transactions in the Ethereum network by contracts that allow transfer of tokens between different blockchains.\n\nThis is the Point-in-Time (PiT) variant of Bridges Transactions (Relative). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_count_bridges_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_count_bridges_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "arbitrum": 0.2472718253968254,
      "axie_infinity": null,
      "hop": null,
      "immutable_x": 0.0441468253968254,
      "multichain": 0.000248015873015873,
      "optimism": 0.012648809523809524,
      "other_bridges": 0.4975198412698413,
      "polygon": 0.0662202380952381,
      "synapse": 0.008680555555555556,
      "wormhole": 0.11879960317460317,
      "zksync": 0.004464285714285714
    }
  }
]

Bridges TVL

get

The Total Value Locked (TVL) in bridges measures the total USD value that is locked within the Ethereum side of bridge smart contracts. Locked tokens are not available on the Ethereum chain, but are available on the target blockchains. An increasing TVL means that value is flowing out of Ethereum and into other target blockchains, whilst a decreasing TVL means the value is flowing back into Ethereum. Bridge TVL is computed daily, by multiplying the number of tokens locked within the bridge smart contracts, by the latest daily price for each token.\n\nBridges are protocols that enable digital assets to be transferred from one blockchain to another. When an asset is transferred out of Ethereum, it gets deposited and locked into a bridge smart contract. When the asset is transferred back to Ethereum, it is withdrawn and released from the smart contract.\n\nThis metric only includes bridge contracts on the Ethereum side. The bridges included in this metric cover bridge deposits into both L1 and L2 blockchains, providing information on the value transferred to both L1 competitors, and L2 scaling solutions. Each bridge included in this metric represents a single blockchain, except the ones labeled as multichain. That label is used to represent bridges that allow transferring assets across multiple different chains.\n\nThis is the Point-in-Time (PiT) variant of Bridges TVL. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/bridges/total_value_locked_by_chain_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/bridges/total_value_locked_by_chain_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "arbitrum": 7370061506.617432,
      "avalanche": 208957146.7142944,
      "aztec": null,
      "boba": null,
      "bsc": null,
      "deversifi": 9028528.040108621,
      "dydx": 179785666.94088715,
      "fantom": null,
      "fuse": null,
      "gluon_network": null,
      "gnosis_chain": 242395496.93540865,
      "harmony": null,
      "heco_chain": null,
      "huobi": null,
      "immutable_x": 16226489.869090756,
      "layer2finance": null,
      "loopring": 37277823.9373375,
      "moonriver": null,
      "multichain": 793340528.2765211,
      "near": 14374091.123601634,
      "optimism": 246208637.46996668,
      "polygon": 1823293760.3411589,
      "ronin": null,
      "rsk": 4245701.734071299,
      "secret_network": null,
      "solana": null,
      "sorare": 18295811.572181914,
      "zkswap": null,
      "zksync": 46933539.760658406
    }
  }
]

Bridges TVL Relative

get

This metric presents the Relative Total Value Locked (TVL dominance) of each target blockchain bridge compared to the total TVL across all bridges. A rising relative TVL indicates that the target blockchain is growing in USD denominated TVL dominance compared to the others (and vice versa). Bridge TVL is computed daily, by multiplying the number of tokens locked within the bridge smart contract, by the latest daily price of each token. Relative TVL is then computed by dividing the TVL of each bridge by the total TVL across all bridges.\n\nBridges are protocols that enable digital assets to be transferred from one blockchain to another. When an asset is transferred out of Ethereum, it gets deposited and locked into a bridge smart contract. When the asset is transferred back to Ethereum, it is withdrawn and released from the smart contract.\n\nThis metric only includes bridge contracts on the Ethereum side. The bridges included in this metric cover bridge deposits into both L1 and L2 blockchains, providing information on the value transferred to both L1 competitors, and L2 scaling solutions. Each bridge included in this metric represents a single blockchain, except the ones labeled as multichain. That label is used to represent bridges that allow transferring assets across multiple different chains.\n\nThis is the Point-in-Time (PiT) variant of Bridges TVL Relative. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/bridges/total_value_locked_by_chain_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/bridges/total_value_locked_by_chain_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "arbitrum": 0.6693712266142606,
      "avalanche": 0.01897811863311817,
      "aztec": null,
      "boba": null,
      "bsc": null,
      "deversifi": 0.0008199981619288349,
      "dydx": 0.016328676809526033,
      "fantom": null,
      "fuse": null,
      "gluon_network": null,
      "gnosis_chain": 0.022015090506876278,
      "harmony": null,
      "heco_chain": null,
      "huobi": null,
      "immutable_x": 0.0014737387764762596,
      "layer2finance": null,
      "loopring": 0.003385684463018594,
      "moonriver": null,
      "multichain": 0.07205358083625907,
      "near": 0.0013054983324401479,
      "optimism": 0.022361411437112465,
      "polygon": 0.16559704145506277,
      "ronin": null,
      "rsk": 0.0003856074437129009,
      "secret_network": null,
      "solana": null,
      "sorare": 0.0016616808181286861,
      "zkswap": null,
      "zksync": 0.004262645712078973
    }
  }
]

Bridges Withdrawals By Chain

get

This metric measures the USD value which is withdrawn from bridge smart contracts on Ethereum, and is therefore flowing into the Ethereum blockchain, and out of target blockchains. Withdrawal Volume is computed daily by multiplying the number of tokens withdrawn from bridges by the latest daily price of each token.\n\nBridges are protocols that enable digital assets to be transferred from one blockchain to another. When an asset is transferred out of Ethereum, it gets deposited and locked into a bridge smart contract. When the asset is transferred back to Ethereum, it is withdrawn and released from the smart contract.\n\nThis metric only includes bridge contracts on the Ethereum side. The bridges included in this metric cover bridge deposits into both L1 and L2 blockchains, providing information on the value transferred to both L1 competitors, and L2 scaling solutions. Each bridge included in this metric represents a single blockchain, except the ones labeled as multichain. That label is used to represent bridges that allow transferring assets across multiple different chains.\n\nThis is the Point-in-Time (PiT) variant of Bridges Withdrawals By Chain. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/bridges/withdrawals_by_chain_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/bridges/withdrawals_by_chain_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "arbitrum": 3438472.9406924266,
      "avalanche": 642033.6753044165,
      "aztec": null,
      "boba": null,
      "bsc": null,
      "deversifi": 465870.4589657778,
      "dydx": 627077.7527140599,
      "fantom": null,
      "fuse": null,
      "gluon_network": null,
      "gnosis_chain": 322154.12944959686,
      "harmony": null,
      "heco_chain": null,
      "huobi": null,
      "immutable_x": 1187.9561496,
      "layer2finance": null,
      "loopring": 19998.642567656236,
      "moonriver": null,
      "multichain": 8055447.335573009,
      "near": 0.473308004958,
      "optimism": 314307.12506215274,
      "polygon": 49209329.26801099,
      "ronin": null,
      "rsk": 0,
      "secret_network": null,
      "solana": null,
      "sorare": 0,
      "zkswap": null,
      "zksync": 1271.402657091264
    }
  }
]

Coinjoin Output Count

get

The total count of indistinguishable outputs in coinjoin transactions. The metric is an aggregate of different coinjoin providers. Note that coinjoin metrics rely on heuristics and statistical information that change over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Coinjoin Output Count. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_from_coinjoins_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_from_coinjoins_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 3200
  }
]

Coinjoin Output Volume

get

The total amount of indistinguishable outputs in coinjoin transactions, i.e. the volume of coins mixed by different coinjoin providers. Note that coinjoin metrics rely on heuristics and statistical information that change over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Coinjoin Output Volume. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_from_coinjoins_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_from_coinjoins_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 663.84991864
  }
]

DeFi Transactions (Absolute)

get

The number of transactions (transaction count) in the Ethereum network by on-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs).\n\nThis is the Point-in-Time (PiT) variant of DeFi Transactions (Absolute). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_count_defi_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_count_defi_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "0x": 4925,
      "1inch": 11625,
      "aave": 1245,
      "compound": 183,
      "etherdelta": 2,
      "idex": null,
      "kyber": 1,
      "metamask": 6494,
      "other_defi": 42267,
      "sushiswap": 302,
      "uniswap": 112300
    }
  }
]

DeFi Transactions (Relative)

get

The relative amount (share) of transactions in the Ethereum network by on-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs).\n\nThis is the Point-in-Time (PiT) variant of DeFi Transactions (Relative). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_count_defi_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_count_defi_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "0x": 0.02746119189936658,
      "1inch": 0.06481956463556071,
      "aave": 0.00694196627709876,
      "compound": 0.0010203854045856009,
      "etherdelta": 0.000011151753055580337,
      "idex": null,
      "kyber": 0.000005575876527790169,
      "metamask": 0.036209742171469356,
      "other_defi": 0.23567557320010707,
      "sushiswap": 0.001683914711392631,
      "uniswap": 0.6261709340708359
    }
  }
]

Depositing Addresses

get

The number of unique addresses that appeared as a sender in a transaction sending funds to exchanges.\n\nThis is the Point-in-Time (PiT) variant of Depositing Addresses. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id (see list below for more details)

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 1month, 1w, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/addresses/sending_to_exchanges_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/addresses/sending_to_exchanges_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 80606
  }
]

Dormancy Flow

get

Dormancy Flow is the ratio of the current market capitalization and the annualized dormancy value (measured in USD). The metric can be used to time market lows and assess whether the bull market remains in relatively normal conditions. It helps confirm whether an asset is in a bullish or bearish primary trend. This metric was put forward by David Puell. For more information please read his introductory article.\n\nThis is the Point-in-Time (PiT) variant of Dormancy Flow. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/dormancy_flow_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/dormancy_flow_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 197733.86082490344
  }
]

Entities Net Growth

get

The net growth of unique entities in the network. This metric is defined as the difference between new entities and "disappearing" entities (entities with a zero balance that had a non–zero balance at the previous timestamp). Entities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThe computation of this metric requires statistical information from several days, and is therefore only available with a lag of one week.\n\nThis is the Point-in-Time (PiT) variant of Entities Net Growth. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/net_growth_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/net_growth_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 12160
  }
]

Entities Supply Distribution

get

Relative distribution of the circulating supply held by entities with specific balance bands.\n\nThis is the Point-in-Time (PiT) variant of Entities Supply Distribution. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/supply_distribution_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/supply_distribution_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "0001_001": 0.002042768398689239,
      "001_01": 0.013303835820954842,
      "01_1": 0.054461581267682774,
      "100_1k": 0.18855360374417587,
      "10_100": 0.16366180178916542,
      "10k_100k": 0.0810959542106678,
      "1_10": 0.10724754396972354,
      "1k_10k": 0.17107059348882758,
      "above_100k": 0.21830394166745087,
      "less_0001": 0.0002583756426620675
    }
  }
]

Entity- and Supply-Adjusted CYD

get

Coin Years Destroyed (CYD) is defined as the 365 day rolling sum of Coin Days Destroyed (CDD), and shows the amount of coin days that have been destroyed over the past year. It is indicative of long-term holder behaviour. This version is entity-adjusted, meaning that transactions within addresses controlled by the same network participant are discarded (see this article for more information), as well as supply-adjusted to account for the increasing baseline of the metric over time. This metric was first put forward by ARK Invest and further developed by Glassnode by adjusting for the circulating supply.\n\nThis is the Point-in-Time (PiT) variant of Entity- and Supply-Adjusted CYD. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/cyd_account_based_supply_adjusted_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/cyd_account_based_supply_adjusted_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 272.6385786626616
  }
]

Entity-Adjusted 90D Coin Days Destroyed (eCDD-90)

get

90D Coin Days Destroyed is the 90 day rolling sum of Coin Days Destroyed (CDD) and shows the amount of coin days that have been destroyed over the past year. This version is entity-adjusted, meaning that transactions within addresses controlled by the same network participant are discarded (see this article for more information), as well as age-adjusted meaning that we normalize by time in order to account for the increasing baseline as time goes by.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted 90D Coin Days Destroyed (eCDD-90). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/cdd90_account_based_age_adjusted_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/cdd90_account_based_age_adjusted_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 260477.7635491613
  }
]

Entity-Adjusted ASOL

get

Entity-adjusted ASOL is an improved variant of ASOL that discards transactions between addresses of the same entity ("in-house" transactions). Entity-adjusted ASOL therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted ASOL. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/asol_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/asol_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 68.93313414413431
  }
]

Entity-Adjusted CDD

get

Entity-adjusted CDD is an improved variant of CDD that discards transactions between addresses of the same entity ("in-house" transactions). Entity-adjusted CDD therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted CDD. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/cdd_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/cdd_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 20846517.089375068
  }
]

Entity-Adjusted CYD

get

Coin Years Destroyed (CYD) is defined as the 365 day rolling sum of Coin Days Destroyed (CDD), and shows the amount of coin days that have been destroyed over the past year. It is indicative of long-term holder behaviour. This version is entity-adjusted, meaning that transactions within addresses controlled by the same network participant are discarded (see this article for more information). This metric was first put forward by ARK Invest.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted CYD. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/cyd_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/cyd_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 5357930237.325099
  }
]

Entity-Adjusted Dormancy

get

Entity-adjusted Dormancy is an improved variant of Average Coin Dormancy that discards transactions between addresses of the same entity ("in-house" transactions). Entity-adjusted Dormancy therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Dormancy. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/dormancy_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/dormancy_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 104.40268080672914
  }
]

Entity-Adjusted Liveliness

get

Entity-adjusted Liveliness is an improved variant of Liveliness that discards transactions between addresses of the same entity ("in-house" transactions). Entity-adjusted Liveliness therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Liveliness. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/liveliness_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/liveliness_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.6204629876583948
  }
]

Entity-Adjusted Long-Term Holder ASOL

get

Long-Term Holder variant of Entity-Adjusted ASOL. Average Spent Output Lifespan (ASOL) is the average age (in days) of spent transaction outputs. Transactions between addresses of the same entity ("in-house" transactions) are discarded. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Long-Term Holder ASOL. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/asol_lth_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/asol_lth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 661.181178802014
  }
]

Entity-Adjusted Long-Term Holder CDD

get

Long-Term Holder variant of Entity-Adjusted CDD. Coin Days Destroyed (CDD) for any given transaction is calculated by taking the number of coins in a transaction and multiplying it by the number of days it has been since those coins were last spent. Transactions between addresses of the same entity ("in-house" transactions) are discarded. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Long-Term Holder CDD. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/cdd_lth_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/cdd_lth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 17261327.421755053
  }
]

Entity-Adjusted Long-Term Holder Dormancy

get

Long-Term Holder variant of Entity-Adjusted Dormancy. Dormancy is the average number of days destroyed per coin transacted, and is defined as the ratio of coin days destroyed and total transfer volume. Transactions between addresses of the same entity ("in-house" transactions) are discarded. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Long-Term Holder Dormancy. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/dormancy_lth_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/dormancy_lth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 461.99480839055263
  }
]

Entity-Adjusted LTH Realized Loss

get

Entity-Adjusted variant of Realized Loss for Long-Term Holders, which denotes the total profit (in USD) of all moved coins whose price at their last movement was lower than the price at the current movement. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH Realized Loss. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/realized_loss_lth_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/realized_loss_lth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 3135518.359679543
  }
]

Entity-Adjusted LTH Realized Loss to Exchanges

get

Entity-Adjusted variant of Realized Loss for coins that are sent from Long-Term Holders to exchanges. Realized loss denotes the total loss (in USD) of all moved coins whose price at their last movement was higher than the price at the current movement. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH Realized Loss to Exchanges. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/realized_loss_lth_to_exchanges_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/realized_loss_lth_to_exchanges_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 232003.4756194142
  }
]

Entity-Adjusted LTH Realized Profit

get

Entity-Adjusted variant of Realized Profit for Long-Term Holders, which denotes the total profit (in USD) of all moved coins whose price at their last movement was lower than the price at the current movement. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH Realized Profit. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/realized_profit_lth_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/realized_profit_lth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 879123108.3164785
  }
]

Entity-Adjusted LTH Realized Profit to Exchanges

get

Entity-Adjusted variant of Realized Profit for coins that are sent from Long-Term Holders to exchanges. Realized profit denotes the total profit (in USD) of all moved coins whose price at their last movement was lower than the price at the current movement. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH Realized Profit to Exchanges. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/realized_profit_lth_to_exchanges_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/realized_profit_lth_to_exchanges_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 16464437.886598842
  }
]

Entity-Adjusted LTH Transfer Volume

get

The total estimated amount of coins moved by long-term holders. Volume transferred within addresses of the same entity is excluded. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH Transfer Volume. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_entity_adjusted_from_lth_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_entity_adjusted_from_lth_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 37362.60041944669
  }
]

Entity-Adjusted LTH Transfer Volume in Loss

get

The total estimated amount of coins moved by long-term holders in loss. Volume transferred within addresses of the same entity is excluded. Coins are considered to be in loss when the price at the time the coins are spent is lower than the entity's average on-chain acquisition price for its funds. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH Transfer Volume in Loss. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_entity_adjusted_from_lth_loss_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_entity_adjusted_from_lth_loss_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 584.2189497835209
  }
]

Entity-Adjusted LTH Transfer Volume in Profit

get

The total estimated amount of coins moved by long-term holders in profit. Volume transferred within addresses of the same entity is excluded. Coins are considered to be in profit when the price at the time the coins are spent is higher than the entity's average on-chain acquisition price for its funds. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH Transfer Volume in Profit. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_entity_adjusted_from_lth_profit_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_entity_adjusted_from_lth_profit_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 36778.38146966315
  }
]

Entity-Adjusted LTH-NUPL

get

Entity-adjusted LTH-NUPL is an improved variant of Long-Term Holders Net Unrealized Profit/Loss (LTH-NUPL) that discards transactions between addresses of the same entity ("in-house" transactions). Entity-adjusted LTH NUPL therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this article. An entity is considered as a Long-Term Holder if the time since its averaged purchasing date is more than 155 days.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH-NUPL. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/nupl_more_155_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/nupl_more_155_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.599533579517488
  }
]

Entity-Adjusted LTH/STH Transfer Volume in Profit/Loss

get

The relative amount of coins moved by by long- and short-term holders in profit/loss. Volume transferred within addresses of the same entity is excluded. Coins are considered to be in profit/loss when the price at the time the coins are spent is higher/lower than the entity's average on-chain acquisition price for its funds. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH/STH Transfer Volume in Profit/Loss. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_entity_adjusted_from_lth_sth_profit_loss_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_entity_adjusted_from_lth_sth_profit_loss_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "lth_loss": 0.0029258616330964256,
      "lth_profit": 0.18419199738273753,
      "sth_loss": 0.13886256848967096,
      "sth_profit": 0.6740195724944952
    }
  }
]

Entity-Adjusted MSOL

get

Entity-adjusted MSOL is an improved variant of MSOL that discards transactions between addresses of the same entity ("in-house" transactions). Entity-adjusted MSOL therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted MSOL. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/msol_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/msol_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 1.8218402777777778
  }
]

Entity-Adjusted MVRV

get

Entity-adjusted MVRV is an improved variant of MVRV Ratio that discards transactions between addresses of the same entity ("in-house" transactions). Entity-adjusted MVRV therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted MVRV. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/mvrv_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/mvrv_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 1.9400974043546526
  }
]

Entity-Adjusted NUPL

get

Entity-adjusted NUPL is an improved variant of Net Unrealized Profit/Loss (NUPL) that discards transactions between addresses of the same entity ("in-house" transactions). Entity-adjusted NUPL therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted NUPL. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/net_unrealized_profit_loss_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/net_unrealized_profit_loss_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.4845702893360587
  }
]

Entity-Adjusted NVT

get

The Network Value to Transactions (NVT) Ratio is computed by dividing the market cap by the transferred on-chain volume measured in USD. This entity-adjusted version of the NVT Ratio uses entity-adjusted on-chain volume and is therefore more accurate as it accounts for actual economic throughput.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted NVT. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/nvt_entity_adjusted_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/nvt_entity_adjusted_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 182.24924158774277
  }
]

Entity-Adjusted Realized Cap

get

Entity-adjusted Realized Cap is an improved variant of Realized Cap that discards transactions between addresses of the same entity ("in-house" transactions). Entity-adjusted Realized Cap therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Realized Cap. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/rcap_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/rcap_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 643512075068.7617
  }
]

Entity-Adjusted Realized Loss

get

Entity-Adjusted variant of Realized Loss, which denotes the total profit (in USD) of all moved coins whose price at their last movement was lower than the price at the current movement.\n\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Realized Loss. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/realized_loss_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/realized_loss_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 15325193.390788589
  }
]

Entity-Adjusted Realized Loss to Exchanges

get

Entity-Adjusted variant of Realized Loss for coins that are sent to exchanges. Realized loss denotes the total loss (in USD) of all moved coins whose price at their last movement was higher than the price at the current movement.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Realized Loss to Exchanges. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/realized_loss_to_exchanges_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/realized_loss_to_exchanges_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 2159468.2663944983
  }
]

Entity-Adjusted Realized Profit

get

Entity-Adjusted variant of Realized Profit, which denotes the total profit (in USD) of all moved coins whose price at their last movement was lower than the price at the current movement.\n\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Realized Profit. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/realized_profit_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/realized_profit_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 1199867034.793109
  }
]

Entity-Adjusted Realized Profit to Exchanges

get

Entity-Adjusted variant of Realized Profit for coins that are sent to exchanges. Realized profit denotes the total profit (in USD) of all moved coins whose price at their last movement was lower than the price at the current movement.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Realized Profit to Exchanges. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/realized_profit_to_exchanges_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/realized_profit_to_exchanges_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 86620913.99723811
  }
]

Entity-Adjusted Short-Term Holder ASOL

get

Short-Term Holder variant of Entity-Adjusted ASOL. Average Spent Output Lifespan (ASOL) is the average age (in days) of spent transaction outputs. Transactions between addresses of the same entity ("in-house" transactions) are discarded. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Short-Term Holder ASOL. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/asol_sth_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/asol_sth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 7.933436207142035
  }
]

Entity-Adjusted Short-Term Holder CDD

get

Short-Term Holder variant of Entity-Adjusted CDD. Coin Days Destroyed (CDD) for any given transaction is calculated by taking the number of coins in a transaction and multiplying it by the number of days it has been since those coins were last spent. Transactions between addresses of the same entity ("in-house" transactions) are discarded. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Short-Term Holder CDD. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/cdd_sth_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/cdd_sth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 3585189.667619669
  }
]

Entity-Adjusted Short-Term Holder Dormancy

get

Short-Term Holder variant of Entity-Adjusted Dormancy. Dormancy is the average number of days destroyed per coin transacted, and is defined as the ratio of coin days destroyed and total transfer volume. Transactions between addresses of the same entity ("in-house" transactions) are discarded. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Short-Term Holder Dormancy. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/dormancy_sth_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/dormancy_sth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 22.088320654354888
  }
]

Entity-Adjusted SOPR

get

Entity-adjusted SOPR is an improved variant of SOPR that discards transactions between addresses of the same entity ("in-house" transactions). Entity-adjusted SOPR therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted SOPR. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/sopr_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/sopr_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 1.1052509300982343
  }
]

Entity-Adjusted Spent Volume Age Bands (SVAB)

get

Spent Volume Age Bands (SVAB) is a separation of the on-chain transfer volume based on the coins' age. Each band represents the percentage of spent volume that was previously moved within the time period denoted in the legend. This metric is entity-adjusted and discards transactions between addresses of the same entity ("in-house" transactions).\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Spent Volume Age Bands (SVAB). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/svab_entity_adjusted_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/svab_entity_adjusted_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "1d_1w": 0.1523432606385792,
      "1m_3m": 0.034203269747369376,
      "1w_1m": 0.14268109088991998,
      "1y_2y": 0.07704889013957367,
      "24h": 0.364938434468095,
      "2y_3y": 0.0031659359115703114,
      "3m_6m": 0.13920771501927032,
      "3y_5y": 0.005876969948760398,
      "5y_7y": 0.0007580399618969412,
      "6m_12m": 0.07641280722913966,
      "7y_10y": 0.001143124011897634,
      "more_10y": 0.0022204620339275408
    }
  }
]

Entity-Adjusted Spent Volume Lifespan < 24h

get

The total transfer volume of coins younger than 24 hours. This metric is entity-adjusted and discards transactions between addresses of the same entity ("in-house" transactions).\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Spent Volume Lifespan < 24h. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/svl_entity_adjusted_24h_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/svl_entity_adjusted_24h_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 72868.77359780001
  }
]

Entity-Adjusted Spent Volume Lifespan > 10y

get

The total transfer volume of coins that were last active more than 10 years ago. This metric is entity-adjusted and discards transactions between addresses of the same entity ("in-house" transactions).\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Spent Volume Lifespan > 10y. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/svl_entity_adjusted_more_10y_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/svl_entity_adjusted_more_10y_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 443.36888075
  }
]

Entity-Adjusted Spent Volume Lifespan 1d-1w

get

The total transfer volume of coins that were last active between 1d and 1w ago. This metric is entity-adjusted and discards transactions between addresses of the same entity ("in-house" transactions).\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Spent Volume Lifespan 1d-1w. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/svl_entity_adjusted_1d_1w_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/svl_entity_adjusted_1d_1w_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 30419.011866490007
  }
]

Entity-Adjusted Spent Volume Lifespan 1m-3m

get

The total transfer volume of coins that were last active between 1m and 3m ago. This metric is entity-adjusted and discards transactions between addresses of the same entity ("in-house" transactions).\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Spent Volume Lifespan 1m-3m. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/svl_entity_adjusted_1m_3m_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/svl_entity_adjusted_1m_3m_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 6829.508991450001
  }
]

Entity-Adjusted Spent Volume Lifespan 1w-1m

get

The total transfer volume of coins that were last active between 1w and 1m ago. This metric is entity-adjusted and discards transactions between addresses of the same entity ("in-house" transactions).\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Spent Volume Lifespan 1w-1m . PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/svl_entity_adjusted_1w_1m_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/svl_entity_adjusted_1w_1m_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 28489.726284649998
  }
]

Entity-Adjusted Spent Volume Lifespan 1y-2y

get

The total transfer volume of coins that were last active between 1y and 2y ago. This metric is entity-adjusted and discards transactions between addresses of the same entity ("in-house" transactions).\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Spent Volume Lifespan 1y-2y. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/svl_entity_adjusted_1y_2y_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/svl_entity_adjusted_1y_2y_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 15384.672046740003
  }
]

Entity-Adjusted Spent Volume Lifespan 2y-3y

get

The total transfer volume of coins that were last active between 2y and 3y ago. This metric is entity-adjusted and discards transactions between addresses of the same entity ("in-house" transactions).\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Spent Volume Lifespan 2y-3y. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/svl_entity_adjusted_2y_3y_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/svl_entity_adjusted_2y_3y_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 632.1555785199998
  }
]

Entity-Adjusted Spent Volume Lifespan 3m-6m

get

The total transfer volume of coins that were last active between 3m and 6m ago. This metric is entity-adjusted and discards transactions between addresses of the same entity ("in-house" transactions).\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Spent Volume Lifespan 3m-6m. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/svl_entity_adjusted_3m_6m_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/svl_entity_adjusted_3m_6m_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 27796.18289203
  }
]

Entity-Adjusted Spent Volume Lifespan 3y-5y

get

The total transfer volume of coins that were last active between 3y and 5y ago. This metric is entity-adjusted and discards transactions between addresses of the same entity ("in-house" transactions).\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Spent Volume Lifespan 3y-5y. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/svl_entity_adjusted_3y_5y_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/svl_entity_adjusted_3y_5y_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 1173.47900958
  }
]

Entity-Adjusted Spent Volume Lifespan 5y-7y

get

The total transfer volume of coins that were last active between 5y and 7y ago. This metric is entity-adjusted and discards transactions between addresses of the same entity ("in-house" transactions).\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Spent Volume Lifespan 5y-7y. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/svl_entity_adjusted_5y_7y_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/svl_entity_adjusted_5y_7y_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 151.36098898999998
  }
]

Entity-Adjusted Spent Volume Lifespan 6m-12m

get

The total transfer volume of coins that were last active between 6m and 12m ago. This metric is entity-adjusted and discards transactions between addresses of the same entity ("in-house" transactions).\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Spent Volume Lifespan 6m-12m . PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/svl_entity_adjusted_6m_12m_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/svl_entity_adjusted_6m_12m_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 15257.662728970003
  }
]

Entity-Adjusted Spent Volume Lifespan 7y-10y

get

The total transfer volume of coins that were last active between 7y and 10y ago. This metric is entity-adjusted and discards transactions between addresses of the same entity ("in-house" transactions).\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Spent Volume Lifespan 7y-10y. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/svl_entity_adjusted_7y_10y_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/svl_entity_adjusted_7y_10y_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 228.25232135000005
  }
]

Entity-Adjusted STH Realized Loss

get

Entity-Adjusted variant of Realized Loss for Short-Term Holders, which denotes the total profit (in USD) of all moved coins whose price at their last movement was lower than the price at the current movement. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted STH Realized Loss. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/realized_loss_sth_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/realized_loss_sth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 12189675.031109048
  }
]

Entity-Adjusted STH Realized Loss to Exchanges

get

Entity-Adjusted variant of Realized Loss for coins that are sent from Short-Term Holders to exchanges. Realized loss denotes the total loss (in USD) of all moved coins whose price at their last movement was higher than the price at the current movement. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted STH Realized Loss to Exchanges. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/realized_loss_sth_to_exchanges_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/realized_loss_sth_to_exchanges_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 1927464.7907750844
  }
]

Entity-Adjusted STH Realized Profit

get

Entity-Adjusted variant of Realized Profit for Short-Term Holders, which denotes the total profit (in USD) of all moved coins whose price at their last movement was lower than the price at the current movement. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted STH Realized Profit. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/realized_profit_sth_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/realized_profit_sth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 320743926.47663045
  }
]

Entity-Adjusted STH Realized Profit to Exchanges

get

Entity-Adjusted variant of Realized Profit for coins that are sent from Short-Term Holders to exchanges. Realized profit denotes the total profit (in USD) of all moved coins whose price at their last movement was lower than the price at the current movement. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted STH Realized Profit to Exchanges. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/realized_profit_sth_to_exchanges_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/realized_profit_sth_to_exchanges_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 70156476.11063927
  }
]

Entity-Adjusted STH Transfer Volume

get

The total estimated amount of coins moved by short-term holders. Volume transferred within addresses of the same entity is excluded. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted STH Transfer Volume. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_entity_adjusted_from_sth_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_entity_adjusted_from_sth_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 162311.5547678732
  }
]

Entity-Adjusted STH Transfer Volume in Loss

get

The total estimated amount of coins moved by short-term holders in loss. Volume transferred within addresses of the same entity is excluded. Coins are considered to be in loss when the price at the time the coins are spent is lower than the entity's average on-chain acquisition price for its funds. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted STH Transfer Volume in Loss. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_entity_adjusted_from_sth_loss_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_entity_adjusted_from_sth_loss_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 27727.266050316397
  }
]

Entity-Adjusted STH Transfer Volume in Profit

get

The total estimated amount of coins moved by short-term holders in profit. Volume transferred within addresses of the same entity is excluded. Coins are considered to be in profit when the price at the time the coins are spent is higher than the entity's average on-chain acquisition price for its funds. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted STH Transfer Volume in Profit. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_entity_adjusted_from_sth_profit_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_entity_adjusted_from_sth_profit_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 134584.28871755683
  }
]

Entity-Adjusted STH-NUPL

get

Entity-adjusted STH-NUPL is an improved variant of Shot-Term Holders Net Unrealized Profit/Loss (STH-NUPL) that discards transactions between addresses of the same entity ("in-house" transactions). Entity-adjusted STH NUPL therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this article. An entity is considered as a Short-Term Holder if the time since its averaged purchasing date is less than 155 days.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted STH-NUPL. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/nupl_less_155_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/nupl_less_155_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.02685545305667467
  }
]

Entity-Adjusted Transaction Count

get

The estimated entity-adjusted number of transactions is defined as the number of transactions between different entities, i.e. the total number of transactions excluding transactions within addresses of the same entity. Entities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses.\n\nFor more information this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Transaction Count. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/entity_adjusted_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/entity_adjusted_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 229425
  }
]

Entity-Adjusted Unrealized Loss

get

Entity-adjusted Relative Unrealized Loss is an improved variant of Unrealized Loss that discards transactions between addresses of the same entity ("in-house" transactions). Entity-adjusted Relative Unrealized Loss therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Unrealized Loss. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/unrealized_loss_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/unrealized_loss_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.006268892329103886
  }
]

Entity-Adjusted Unrealized Profit

get

Entity-adjusted Relative Unrealized Profit is an improved variant of Unrealized Profit that discards transactions between addresses of the same entity ("in-house" transactions). Entity-adjusted Relative Unrealized Proft therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Unrealized Profit. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/unrealized_profit_account_based_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/unrealized_profit_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.4908391816651626
  }
]

Entity-Adjusted URPD

get

UTXO Realized Price Distribution (URPD) shows at which prices the current set of Bitcoin UTXOs were created, i.e. each bar shows the amount of existing bitcoins that last moved within that specified price bucket. This version is entity-adjusted, meaning that for each entity the average purchasing price is used to sort its full balance into a bucket. In this calculation we discard coin movements between addresses controlled by the same entity, as such transfers do not correspond to real purchasing events and would distort the actual mean purchasing price. Further, we exclude all supply that is on exchanges, because a single averaged price for the funds of millions of users would be misleading and give rise to unwanted artifacts in the data.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted URPD. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

istringOptional

frequency interval - 24h

fstring · enumOptional

format - json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/urpd_entity_adjusted_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/urpd_entity_adjusted_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "ath_price": 73616.068025447,
    "current_price": 63122.179998599,
    "total_supply": 19756758.544971,
    "partitions": [
      3733490.86863736,
      264696.65574535,
      44616.81368859,
      180554.2382778,
      190601.05124081002,
      195750.2948684,
      65048.6554688,
      108903.06026501,
      192550.25642715002,
      272994.63098065,
      144191.64974219,
      233821.06561094002,
      198753.04695109001,
      156702.16452974,
      144582.21493092,
      134646.96375280002,
      56808.57534427,
      49584.34115782,
      47884.04670252,
      44010.31584611,
      35934.90863131,
      51143.00224488,
      333645.65294314,
      123536.11478029001,
      62217.019372840005,
      87429.26649213,
      240574.48912481,
      109787.85523045,
      118770.6280839,
      86323.01839694,
      86758.43773689,
      144587.78178731,
      93118.87510069,
      55799.58931761,
      42612.72147812,
      365412.87558306,
      197739.86116006,
      136308.18275002,
      130943.07116986,
      171186.34769319,
      164502.22682935,
      190238.54323092,
      275972.5343721,
      56012.747876270005,
      52782.858299370004,
      54666.027034,
      79492.05811414,
      76729.7309261,
      209991.85093814,
      102936.41512496,
      102122.99589626,
      111493.16205206,
      78578.55095442,
      147160.81551193,
      111435.68429055001,
      82065.20226854,
      136363.15657026,
      138963.51322006,
      141274.61417686,
      149193.68364473002,
      59996.824356080004,
      54615.6789834,
      72476.69925143001,
      75658.03772312,
      231168.71430173,
      70290.69474828,
      60051.971495570004,
      55769.76355351,
      48915.18014844,
      64208.59201619,
      106077.14912246,
      41996.07044401,
      43401.45786105,
      75896.4530195,
      70561.99019363,
      89740.54758193,
      111020.87513715,
      185788.61782478,
      217143.60178478,
      144930.2910115,
      230084.1981463,
      199600.0256637,
      232688.68963091,
      289959.45522173,
      164846.21432802,
      252445.69363481,
      199896.50012082,
      320012.85077886,
      117206.24201445,
      160903.35386243,
      180873.31123441,
      205838.52160277,
      123805.3126069,
      118168.61043513,
      123952.60162413001,
      86191.24511344,
      84890.37528694,
      63045.9538742,
      75347.595965,
      65441.220847870005
    ],
    "prices": [
      0,
      736.1606802544701,
      1472.3213605089402,
      2208.48204076341,
      2944.6427210178804,
      3680.8034012723506,
      4416.96408152682,
      5153.1247617812905,
      5889.285442035761,
      6625.44612229023,
      7361.606802544701,
      8097.7674827991705,
      8833.92816305364,
      9570.08884330811,
      10306.249523562581,
      11042.410203817051,
      11778.570884071522,
      12514.73156432599,
      13250.89224458046,
      13987.052924834932,
      14723.213605089402,
      15459.37428534387,
      16195.534965598341,
      16931.69564585281,
      17667.85632610728,
      18404.01700636175,
      19140.17768661622,
      19876.338366870692,
      20612.499047125162,
      21348.659727379632,
      22084.820407634103,
      22820.981087888573,
      23557.141768143043,
      24293.302448397513,
      25029.46312865198,
      25765.62380890645,
      26501.78448916092,
      27237.94516941539,
      27974.105849669864,
      28710.266529924334,
      29446.427210178805,
      30182.587890433275,
      30918.74857068774,
      31654.90925094221,
      32391.069931196682,
      33127.23061145115,
      33863.39129170562,
      34599.55197196009,
      35335.71265221456,
      36071.87333246903,
      36808.0340127235,
      37544.19469297797,
      38280.35537323244,
      39016.516053486914,
      39752.676733741384,
      40488.837413995854,
      41224.998094250324,
      41961.158774504795,
      42697.319454759265,
      43433.48013501373,
      44169.640815268205,
      44905.80149552267,
      45641.962175777146,
      46378.12285603161,
      47114.283536286086,
      47850.444216540556,
      48586.60489679503,
      49322.7655770495,
      50058.92625730396,
      50795.08693755844,
      51531.2476178129,
      52267.40829806738,
      53003.56897832184,
      53739.72965857632,
      54475.89033883078,
      55212.05101908525,
      55948.21169933973,
      56684.37237959419,
      57420.53305984867,
      58156.69374010313,
      58892.85442035761,
      59629.01510061207,
      60365.17578086655,
      61101.33646112101,
      61837.49714137548,
      62573.65782162995,
      63309.81850188442,
      64045.9791821389,
      64782.139862393364,
      65518.30054264784,
      66254.4612229023,
      66990.62190315677,
      67726.78258341124,
      68462.94326366571,
      69199.10394392018,
      69935.26462417466,
      70671.42530442913,
      71407.5859846836,
      72143.74666493807,
      72879.90734519254
    ]
  }
]

Entity-Adjusted Volume (Mean)

get

The mean estimated amount of coins moved between different entities, i.e. excluding the volume transferred within addresses of the same entity. Entities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses.\n\nFor more information this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Volume (Mean). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_entity_adjusted_mean_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_entity_adjusted_mean_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.8703243115934095
  }
]

Entity-Adjusted Volume (Median)

get

The median estimated amount of coins moved between different entities, i.e. excluding volume transferred within addresses of the same entity. Entities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses.\n\nFor more information this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Volume (Median). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_entity_adjusted_median_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_entity_adjusted_median_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.0017897
  }
]

Entity-Adjusted Volume (Total)

get

The total estimated amount of coins moved between different entities, i.e. the total volumed transferred excluding the volume transferred within addresses of the same entity. Entities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses.\n\nFor more information this article.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Volume (Total). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_entity_adjusted_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_entity_adjusted_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 199674.15518732
  }
]

ERC-20 Transactions (Absolute)

get

The number of transactions (transaction count) in the Ethereum network by transactions calling ERC20 contracts. Stablecoins contracts are excluded here.\n\nThis is the Point-in-Time (PiT) variant of ERC-20 Transactions (Absolute). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_count_erc20_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_count_erc20_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "ape": 502,
      "bat": 178,
      "bnb": 73,
      "cro": 414,
      "leo": 4,
      "link": 2116,
      "mana": 358,
      "matic": 3808,
      "other_erc20s": 150312,
      "sand": 305,
      "shib": 2720,
      "snx": 215,
      "uni": 635,
      "wbtc": 982,
      "weth": 4792
    }
  }
]

ERC-20 Transactions (Relative)

get

The relative amount (share) of transactions in the Ethereum network by transactions calling ERC20 contracts. Stablecoins contracts are excluded here.\n\nThis is the Point-in-Time (PiT) variant of ERC-20 Transactions (Relative). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_count_erc20_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_count_erc20_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "ape": 0.002998554481704039,
      "bat": 0.0010632324656241413,
      "bnb": 0.0004360447752278782,
      "cro": 0.0024729114649909806,
      "leo": 0.00002389286439604812,
      "link": 0.012639325265509456,
      "mana": 0.0021384113634463067,
      "matic": 0.02274600690503781,
      "other_erc20s": 0.8978460582746962,
      "sand": 0.0018218309101986692,
      "shib": 0.016247147789312723,
      "snx": 0.0012842414612875865,
      "uni": 0.003792992222872639,
      "wbtc": 0.005865698209229814,
      "weth": 0.028623651546465647
    }
  }
]

ETH 2.0 Total Value Staked by Provider

get

The total amount of ETH transferred to the ETH2 deposit contract via staking providers.\n\nThis is the Point-in-Time (PiT) variant of ETH 2.0 Total Value Staked by Provider. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/eth2/deposited_by_provider_volume_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/eth2/deposited_by_provider_volume_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "abyssfinance": 1190336,
      "ankr": 58112,
      "binance": 2307584.01809,
      "bitcoinsuisse": 449952,
      "bitstamp": 96128,
      "coinbase": 2064256.0395556598,
      "figment": 1702720,
      "huobi": 127584,
      "kraken": 2202272,
      "lido": 11952096,
      "okex": 720066,
      "rocketpool": 450688,
      "stakedus": 1060800,
      "stakefish": 828608,
      "stakewise": 100928
    }
  }
]

EU Year-over-Year Supply Change

get

\nThis metric aims at giving an estimate for the year-over-year change in the share of the Bitcoin supply to be held/traded in Europe.\n\nGeolocation of Bitcoin supply is performed probabilistically at the entity level. The timestamps of all transactions created by an entity are correlated with the working hours of different geographical regions to determine the probabilities for each entity being located in the US, Europe, or Asia. Working hours are defined as:\n\n* US: 8am to 8pm Eastern Time (13:00-01:00 UTC)\n* EU: 8am to 8pm Central European Time (07:00-19:00 UTC)\n* Asia: 8am to 8pm China Standard Time (00:00-12:00 UTC)\n\nAn entity's balance will only contribute to the supply in the respective region if the location can be determined with a high certainty. Supply held on exchanges wallets are excluded.\n \n\nThis is the Point-in-Time (PiT) variant of EU Year-over-Year Supply Change. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/emea_1y_supply_change_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/emea_1y_supply_change_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": -0.0008315373192647191
  }
]

Exchange Balance (Percent)

get

The percent supply held on exchange addresses. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Exchange Balance (Percent). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id (see list below for more details)

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/distribution/balance_exchanges_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/distribution/balance_exchanges_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.15107197885900217
  }
]

Exchange Balance (Stacked)

get

The total amount of coins held on exchange addresses. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Exchange Balance (Stacked). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC, ETH, BNB, DOGE, TON, TRX, XRP

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/distribution/balance_exchanges_all_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/distribution/balance_exchanges_all_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "binance": 687172.19624459,
      "bitfinex": 354723.08924153,
      "bitget": 19561.78212826,
      "bithumb": 18102.22683284,
      "bitmex": 53900.09533312,
      "bitstamp": 49847.12412036,
      "bittrex": 173889.15836652002,
      "bybit": 55849.02422702,
      "coinbase": 859912.6617068701,
      "coincheck": 46296.10891625,
      "coinex": 2313.2398519,
      "crypto.com": 51725.87136978,
      "deribit": 39465.08120986,
      "ftx": 13.34624367,
      "gate.io": 13100.70148519,
      "gemini": 131513.03561107,
      "hitbtc": 56751.67666139,
      "huobi": 12402.66073926,
      "korbit": 7176.86552778,
      "kraken": 181512.05839703,
      "kucoin": 13738.80886257,
      "luno": 1425.8791213,
      "okex": 136683.60374003,
      "poloniex": 11319.09383421,
      "swissborg": 6296.74735593
    }
  }
]

Exchange Balance (Total)

get

The total amount of coins held on exchange addresses. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Exchange Balance (Total). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id (see list below for more details)

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/distribution/balance_exchanges_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/distribution/balance_exchanges_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 2984692.13712833
  }
]

Exchange Deposits

get

The total count of transfers to exchange addresses, i.e. the number of on-chain deposits to exchanges. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Exchange Deposits. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id (see list below for more details)

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_to_exchanges_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_to_exchanges_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 55678
  }
]

Exchange Fee Dominance

get

The Exchange Fee Dominance metric is defined as the percent amount of total fees paid in transactions related to on-chain exchange activity.\n- Deposits: Transactions that include an exchange address as the receiver of funds.\n- Withdrawals: Transactions that include an exchange address as the sender of funds.\n- In-House: Transactions that include addresses of a single exchange as both the sender and receiver of funds.\n- Inter-Exchange: Transactions that include addresses of (distinct) exchanges as both the sender and receiver of funds.\n\nIf a transaction can be categorized into multiple of these categories (e.g. a transaction that sends funds externally as well as in-house), the fees are split into percentages according to the volume transferred.\n\nThis is the Point-in-Time (PiT) variant of Exchange Fee Dominance. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC, ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/fees/exchanges_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/fees/exchanges_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "deposit": 0.10249168228842816,
      "inhouse": 0.09819328957331763,
      "inter": 0.0031369419769756634,
      "total": 0.21733112694292328,
      "withdrawal": 0.0135092131042018
    }
  }
]

Exchange Fees (Mean)

get

The mean amount of fees paid in transactions related to on-chain exchange activity. Note that the mean is computed over transfers, not transactions.\n- Deposits: Transactions that include an exchange address as the receiver of funds.\n- Withdrawals: Transactions that include an exchange address as the sender of funds.\n- In-House: Transactions that include addresses of a single exchange as both the sender and receiver of funds.\n- Inter-Exchange: Transactions that include addresses of (distinct) exchanges as both the sender and receiver of funds.\n\nIf a transaction can be categorized into multiple of these categories (e.g. a transaction that sends funds externally as well as in-house), the fees are split into percentages according to the volume transferred.\n\nThis is the Point-in-Time (PiT) variant of Exchange Fees (Mean). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC, ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/fees/exchanges_mean_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/fees/exchanges_mean_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "deposit": 0.000018483064812909667,
      "inhouse": 0.00013018286021795775,
      "inter": 0.000009317397709848807,
      "total": 0.00002226776234528911,
      "withdrawal": 0.000004324629827684215
    }
  }
]

Exchange Fees (Total)

get

The total amount of fees paid in transactions related to on-chain exchange activity.\n- Deposits: Transactions that include an exchange address as the receiver of funds.\n- Withdrawals: Transactions that include an exchange address as the sender of funds.\n- In-House: Transactions that include addresses of a single exchange as both the sender and receiver of funds.\n- Inter-Exchange: Transactions that include addresses of (distinct) exchanges as both the sender and receiver of funds.\n\nIf a transaction can be categorized into multiple of these categories (e.g. a transaction that sends funds externally as well as in-house), the fees are split into percentages according to the volume transferred.\n\nThis is the Point-in-Time (PiT) variant of Exchange Fees (Total). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC, ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/fees/exchanges_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/fees/exchanges_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "deposit": 0.9701945550944413,
      "inhouse": 0.9295056219562183,
      "inter": 0.02969454650128815,
      "total": 2.0572740275565704,
      "withdrawal": 0.12787930400462225
    }
  }
]

Exchange Inflow Volume (Mean)

get

The mean value of a transfer to exchanges addresses. Only successful transfers are counted. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Exchange Inflow Volume (Mean). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id (see list below for more details)

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_to_exchanges_mean_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_to_exchanges_mean_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.6965433001087298
  }
]

Exchange Inflow Volume (Total)

get

The total amount of coins transferred to exchange addresses. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Exchange Inflow Volume (Total). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id (see list below for more details)

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_to_exchanges_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_to_exchanges_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 38782.137863453856
  }
]

Exchange Net Position Change

get

The 30d change of the supply held in exchange wallets.\n\nThis is the Point-in-Time (PiT) variant of Exchange Net Position Change. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id (see list below for more details)

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/distribution/exchange_net_position_change_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/distribution/exchange_net_position_change_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": -44347.03098650044
  }
]

Exchange Netflow Volume

get

The difference in volume flowing into exchanges and out of exchanges, i.e. the net flow of coins into/out of exchanges. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Exchange Netflow Volume. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id (see list below for more details)

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_exchanges_net_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_exchanges_net_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": -896.4388651075278
  }
]

Exchange Netflow Volume by Size

get

Breakdown of the net flow of coins into/out of exchanges by the USD value of the transactions. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable - the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Exchange Netflow Volume by Size. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC, ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_exchanges_net_by_size_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_exchanges_net_by_size_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "100k_to_1m": 117.81797035166832,
      "10k_to_100k": 371.2389674201062,
      "1m_to_10m": -837.5050023700002,
      "less_than_10k": 340.70166590068766,
      "more_than_10m": -888.6924664099943
    }
  }
]

Exchange Outflow Volume (Mean)

get

The mean value of a transfer from exchanges addresses. Only successful transfers are counted. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Exchange Outflow Volume (Mean). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id (see list below for more details)

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_from_exchanges_mean_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_from_exchanges_mean_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 1.2121888225509847
  }
]

Exchange Outflow Volume (Total)

get

The total amount of coins transferred from exchange addresses. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Exchange Outflow Volume (Total). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id (see list below for more details)

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_from_exchanges_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_from_exchanges_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 39678.576728561384
  }
]

Exchange Withdrawals

get

The total count of transfers from exchange addresses, i.e. the number of on-chain withdrawals from exchanges. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Exchange Withdrawals. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id (see list below for more details)

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_from_exchanges_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_from_exchanges_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 32733
  }
]

Gas Usage by Bridges (Absolute)

get

The amount of gas consumed by the Ethereum network by contracts that allow transfer of tokens between different blockchains.\n\nThis is the Point-in-Time (PiT) variant of Gas Usage by Bridges (Absolute). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/fees/gas_used_sum_bridges_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/fees/gas_used_sum_bridges_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "arbitrum": 161759604,
      "axie_infinity": null,
      "hop": null,
      "immutable_x": 18128426,
      "multichain": 77343,
      "optimism": 7887156,
      "other_bridges": 241181923,
      "polygon": 46631976,
      "synapse": 4717027,
      "wormhole": 78860957,
      "zksync": 10265193
    }
  }
]

Gas Usage by Bridges (Relative)

get

The relative amount (share) of gas consumed by the Ethereum network by contracts that allow transfer of tokens between different blockchains.\n\nThis is the Point-in-Time (PiT) variant of Gas Usage by Bridges (Relative). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/fees/gas_used_sum_bridges_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/fees/gas_used_sum_bridges_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "arbitrum": 0.001497504,
      "axie_infinity": null,
      "hop": null,
      "immutable_x": 0.000167823,
      "multichain": 7.16e-7,
      "optimism": 0.000073001,
      "other_bridges": 0.002232859,
      "polygon": 0.000431635,
      "synapse": 0.000043659,
      "wormhole": 0.00072996,
      "zksync": 0.00009502
    }
  }
]

Gas Usage by DeFi (Absolute)

get

The amount of gas consumed by the Ethereum network by on-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs).\n\nThis is the Point-in-Time (PiT) variant of Gas Usage by DeFi (Absolute). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/fees/gas_used_sum_defi_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/fees/gas_used_sum_defi_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "0x": 1326930355,
      "1inch": 1992560360,
      "aave": 92791940,
      "compound": 23056158,
      "etherdelta": 63172,
      "idex": null,
      "kyber": 46375,
      "metamask": 1467157518,
      "other_defi": 7264786850,
      "sushiswap": 20848708,
      "uniswap": 20182513160
    }
  }
]

Gas Usage by DeFi (Relative)

get

The relative amount (share) of gas consumed by the Ethereum network by on-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs).\n\nThis is the Point-in-Time (PiT) variant of Gas Usage by DeFi (Relative). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/fees/gas_used_sum_defi_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/fees/gas_used_sum_defi_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "0x": 0.012282514,
      "1inch": 0.018443895,
      "aave": 0.000858961,
      "compound": 0.000213415,
      "etherdelta": 5.84e-7,
      "idex": null,
      "kyber": 4.29e-7,
      "metamask": 0.013580482,
      "other_defi": 0.067245639,
      "sushiswap": 0.000192984,
      "uniswap": 0.186815468
    }
  }
]

Gas Usage by ERC-20 Tokens (Absolute)

get

The amount of gas consumed by the Ethereum network by transactions calling ERC20 contracts. Stablecoins contracts are excluded here.\n\nThis is the Point-in-Time (PiT) variant of Gas Usage by ERC-20 Tokens (Absolute). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/fees/gas_used_sum_erc20_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/fees/gas_used_sum_erc20_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "ape": 20169297,
      "bat": 6837981,
      "bnb": 3227427,
      "cro": 17354332,
      "leo": 508161,
      "link": 85918284,
      "mana": 14878307,
      "matic": 155975134,
      "other_erc20s": 8075113941,
      "sand": 11935911,
      "shib": 110836945,
      "snx": 21537079,
      "uni": 28615444,
      "wbtc": 43806978,
      "weth": 182588543
    }
  }
]

Gas Usage by ERC-20 Tokens (Relative)

get

The relative amount (share) of gas consumed by the Ethereum network by transactions calling ERC20 contracts. Stablecoins contracts are excluded here.\n\nThis is the Point-in-Time (PiT) variant of Gas Usage by ERC-20 Tokens (Relative). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/fees/gas_used_sum_erc20_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/fees/gas_used_sum_erc20_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "ape": 0.000186679,
      "bat": 0.00006329,
      "bnb": 0.000029867,
      "cro": 0.000160659,
      "leo": 0.000004703,
      "link": 0.000795408,
      "mana": 0.000137707,
      "matic": 0.001444036,
      "other_erc20s": 0.07474431,
      "sand": 0.00011047,
      "shib": 0.001025797,
      "snx": 0.000199343,
      "uni": 0.00026488,
      "wbtc": 0.000405442,
      "weth": 0.001690394
    }
  }
]

Gas Usage by NFTs (Absolute)

get

The amount of gas consumed by the Ethereum network by transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\n\nThis is the Point-in-Time (PiT) variant of Gas Usage by NFTs (Absolute). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/fees/gas_used_sum_nfts_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/fees/gas_used_sum_nfts_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "blur.io": 301308420,
      "cryptokitties": 96944,
      "looksrare": 4566901,
      "opensea": 236393000,
      "other_nft_transactions": 979476598,
      "rarible": 1229095,
      "superrare": 4913802
    }
  }
]

Gas Usage by NFTs (Relative)

get

The relative amount (share) of gas consumed by the Ethereum network by transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\n\nThis is the Point-in-Time (PiT) variant of Gas Usage by NFTs (Relative). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/fees/gas_used_sum_nfts_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/fees/gas_used_sum_nfts_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "blur.io": 0.002788979,
      "cryptokitties": 8.97e-7,
      "looksrare": 0.000042271,
      "opensea": 0.002188113,
      "other_nft_transactions": 0.009066223,
      "rarible": 0.000011377,
      "superrare": 0.000045482
    }
  }
]

Gas Usage by Stablecoins (Absolute)

get

The amount of gas consumed by the Ethereum network by stablecoin transactions. Stablecoin are fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\n\nThis is the Point-in-Time (PiT) variant of Gas Usage by Stablecoins (Absolute). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/fees/gas_used_sum_stablecoins_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/fees/gas_used_sum_stablecoins_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "busd": 1085009,
      "dai": 81567283,
      "gusd": 921365,
      "other_stablecoins": 47829056,
      "sai": 48673,
      "tusd": 2367052,
      "usda": null,
      "usdc": 1600795815,
      "usdp": 3480129,
      "usdt": 5221205039,
      "ust": 217454
    }
  }
]

Gas Usage by Stablecoins (Relative)

get

The relative amount (share) of gas consumed by the Ethereum network by stablecoin transactions. Stablecoin are fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\n\nThis is the Point-in-Time (PiT) variant of Gas Usage by Stablecoins (Relative). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/fees/gas_used_sum_stablecoins_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/fees/gas_used_sum_stablecoins_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "busd": 0.000010041,
      "dai": 0.000754924,
      "gusd": 0.000008529,
      "other_stablecoins": 0.000442672,
      "sai": 4.51e-7,
      "tusd": 0.000021913,
      "usda": null,
      "usdc": 0.014815706,
      "usdp": 0.000032214,
      "usdt": 0.04832672,
      "ust": 0.000002012
    }
  }
]

Gas Usage by Transaction Type (Absolute)

get

The amount of gas consumed by the Ethereum network by category. Transactions are classified into the following categories:\n\n- Vanilla: Pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\n\n- ERC20: All transactions calling ERC20 contracts. Contracts in the Stablecoins category are excluded here.\n\n- Stablecoins: Fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\n\n- DeFi: On-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs). We include over 90+ DeFi protocols in this category, such as Uniswap, Etherdelta, 1inch, Sushiswap, Aave, and 0x.\n\n- Bridges: Contracts allowing transfer of tokens between different blockchains. We include 50+ bridges in this category, such as Ronin, Polygon, Optimism, and Arbitrum.\n\n- NFTs: Transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\n\n- MEV Bots: Miner Extractable Value (MEV) bots execute transactions for profit by reordering, inserting, and censoring transactions within blocks.\n\n- Other: This category includes all other transactions in the Ethereum network that are not included in categories listed above.\n\nThis is the Point-in-Time (PiT) variant of Gas Usage by Transaction Type (Absolute). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/fees/tx_types_breakdown_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/fees/tx_types_breakdown_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "bridge": 569509605,
      "defi": 32420907119,
      "erc20": 8749974488,
      "mev-bot": 691613721,
      "nft_transfer": 1524880025,
      "other": 49547953799,
      "stablecoin": 6959516875,
      "vanilla": 7569760076
    }
  }
]

Gas Usage by Transaction Type (Relative)

get

The relative amount (share) of gas consumed by the Ethereum network by category. Transactions are classified into one of the following categories:\n\n- Vanilla: Pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\n\n- ERC20: All transactions calling ERC20 contracts. Contracts in the Stablecoins category are excluded here.\n\n- Stablecoins: Fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\n\n- DeFi: On-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs). We include over 90+ DeFi protocols in this category, such as Uniswap, Etherdelta, 1inch, Sushiswap, Aave, and 0x.\n\n- Bridges: Contracts allowing transfer of tokens between different blockchains. We include 50+ bridges in this category, such as Ronin, Polygon, Optimism, and Arbitrum.\n\n- NFTs: Transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\n\n- MEV Bots: Miner Extractable Value (MEV) bots execute transactions for profit by reordering, inserting, and censoring transactions within blocks.\n\n- Other: This category includes all other transactions in the Ethereum network that are not included in categories listed above.\n\nThis is the Point-in-Time (PiT) variant of Gas Usage by Transaction Type (Relative). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/fees/tx_types_breakdown_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/fees/tx_types_breakdown_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "bridge": 0.005271571,
      "defi": 0.300098787,
      "erc20": 0.080992697,
      "mev-bot": 0.006401808,
      "nft_transfer": 0.0141148,
      "other": 0.458632474,
      "stablecoin": 0.064419621,
      "vanilla": 0.070068237
    }
  }
]

Gas Usage by Vanilla Transactions (Absolute)

get

The amount of gas consumed by the Ethereum network by vanilla transactions. Vanilla transactions are pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called. Note that occasionally the value of the last datapoint can slightly change as some addresses initially transact as "vanilla" before their associated smart contract deployment is observed.\n\nThis is the Point-in-Time (PiT) variant of Gas Usage by Vanilla Transactions (Absolute). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/fees/gas_used_sum_vanilla_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/fees/gas_used_sum_vanilla_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "exchange": 2230583645,
      "vanilla": 6341876508
    }
  }
]

Gas Usage by Vanilla Transactions (Relative)

get

The relative amount (share) of gas consumed by the Ethereum network by vanilla transactions. Vanilla transactions are pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called. Note that occasionally the value of the last datapoint can slightly change as some addresses initially transact as "vanilla" before their associated smart contract deployment is observed.\n\nThis is the Point-in-Time (PiT) variant of Gas Usage by Vanilla Transactions (Relative). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/fees/gas_used_sum_vanilla_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/fees/gas_used_sum_vanilla_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "exchange": 0.020624718,
      "vanilla": 0.058588341
    }
  }
]

German Government Balance

get

The German Government Balance corresponds to the amount of BTC held in addresses controlled by German authorities. The metric includes seized funds, e.g. from Movie2k that were seized by the German BKA. We constantly keep updating the set of addresses contributing to the total balance.\n\nThis is the Point-in-Time (PiT) variant of German Government Balance. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/distribution/balance_german_government_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/distribution/balance_german_government_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.00682807
  }
]

Gini Coefficient

get

The gini coefficient for the distribution of coins over addresses. Exchange addresses, smart contract addresses, and other special asset-specific addresses (e.g. team fund addresses) are excluded for the computation of the gini.\n\nThis is the Point-in-Time (PiT) variant of Gini Coefficient. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/distribution/gini_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/distribution/gini_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.9950503142225519
  }
]

Herfindahl Index

get

Originally used as a measure of competition, we adapt the Herfindahl Index as a metric for decentralization. It measures the addresses' shares of the current supply, and is defined as the sum of weighted address balances in the network. A large score indicates high concentration of supply, whereas a small score is an indicator for more evenly distributed funds across addresses. Exchange addresses, smart contract addresses and other special asset-specific addresses (e.g. team fund addresses) are excluded.\n\nThis is the Point-in-Time (PiT) variant of Herfindahl Index. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/distribution/herfindahl_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/distribution/herfindahl_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.001061291638980749
  }
]

Highly Liquid Supply

get

The total supply held by "highly liquid" entities. The liquidity of an entity is defined as the ratio of cumulative outflows and cumulative inflows over the entity's lifespan. An entity is considered to be illiquid / liquid / highly liquid if its liquidity L is ≲ 0.25 / 0.25 ≲ L ≲ 0.75 / 0.75 ≲ L, respectively. For more information see our introductory article on Bitcoin liquidity.\n\nThis is the Point-in-Time (PiT) variant of Highly Liquid Supply. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/highly_liquid_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/highly_liquid_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 3623868.386403468
  }
]

Illiquid Supply

get

The total supply held by illiquid entities. The liquidity of an entity is defined as the ratio of cumulative outflows and cumulative inflows over the entity's lifespan. An entity is considered to be illiquid / liquid / highly liquid if its liquidity L is ≲ 0.25 / 0.25 ≲ L ≲ 0.75 / 0.75 ≲ L, respectively. For more information see our introductory article on Bitcoin liquidity.\n\nThis is the Point-in-Time (PiT) variant of Illiquid Supply. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/illiquid_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/illiquid_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 14673063.891058806
  }
]

Illiquid Supply Change

get

The monthly (30d) net change of supply held by illiquid entities. For more information see our introductory article on Bitcoin liquidity.\n\nThis is the Point-in-Time (PiT) variant of Illiquid Supply Change. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/illiquid_change_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/illiquid_change_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 181654.73904808797
  }
]

In-House Exchange Volume

get

The total amount of coins transferred within wallets of the same exchange. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of In-House Exchange Volume. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id (see list below for more details)

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_within_exchanges_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_within_exchanges_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 139258.03766922612
  }
]

Inter-Exchange Transfers

get

The total count of transfers between exchanges. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Inter-Exchange Transfers. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id (see list below for more details)

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

from_exchangestringOptional

from_exchange name (see /v1/metrics/transactions/transfers_between_exchanges_count_pit/flows for a full list)

to_exchangestringOptional

to_exchange name (see /v1/metrics/transactions/transfers_between_exchanges_count_pit/flows for a full list)

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_between_exchanges_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_between_exchanges_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 6
  }
]

Inter-Exchange Volume

get

The total amount of coins transferred between exchanges. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Inter-Exchange Volume. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id (see list below for more details)

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

from_exchangestringOptional

from_exchange name (see /v1/metrics/transactions/transfers_volume_between_exchanges_sum_pit/flows for a full list)

to_exchangestringOptional

to_exchange name (see /v1/metrics/transactions/transfers_volume_between_exchanges_sum_pit/flows for a full list)

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_between_exchanges_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_between_exchanges_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 21.72169065
  }
]

Liquid and Illiquid Supply

get

The total supply held by illiquid, liquid, and highly liquid entities. The liquidity of an entity is defined as the ratio of cumulative outflows and cumulative inflows over the entity's lifespan. An entity is considered to be illiquid / liquid / highly liquid if its liquidity L is ≲ 0.25 / 0.25 ≲ L ≲ 0.75 / 0.75 ≲ L, respectively. For more information see our introductory article on Bitcoin liquidity.\n\nThis is the Point-in-Time (PiT) variant of Liquid and Illiquid Supply. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/liquid_illiquid_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/liquid_illiquid_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "highly_liquid": 3623868.386403468,
      "illiquid": 14673063.891058806,
      "liquid": 1459820.0175085573
    }
  }
]

Liquid Supply

get

The total supply held by "liquid" entities. The liquidity of an entity is defined as the ratio of cumulative outflows and cumulative inflows over the entity's lifespan. An entity is considered to be illiquid / liquid / highly liquid if its liquidity L is ≲ 0.25 / 0.25 ≲ L ≲ 0.75 / 0.75 ≲ L, respectively. For more information see our introductory article on Bitcoin liquidity.\n\nThis is the Point-in-Time (PiT) variant of Liquid Supply. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/liquid_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/liquid_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 1459820.0175085573
  }
]

Liquid Supply Change

get

The monthly (30d) net change of supply held by liquid and highly liquid entities. For more information see our introductory article on Bitcoin liquidity.\n\nThis is the Point-in-Time (PiT) variant of Liquid Supply Change. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/liquid_change_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/liquid_change_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": -168107.8640480889
  }
]

Long-Term Holder in Loss to Exchanges (Volume)

get

The total amount of coins transferred from long-term holders in loss to exchange wallets. Only direct transfers are counted. Coins are considered to be in loss when the price at the time the coins are spent is lower than the entity's average on-chain acquisition price for its funds. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Long-Term Holder in Loss to Exchanges (Volume). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_lth_to_exchanges_loss_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_lth_to_exchanges_loss_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 54.77108136842165
  }
]

Long-Term Holder in Profit to Exchanges (Volume)

get

The total amount of coins transferred from long-term holders in profit to exchange wallets. Only direct transfers are counted. Coins are considered to be in profit when the price at the time the coins are spent is higher than the entity's average on-chain acquisition price for its funds. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Long-Term Holder in Profit to Exchanges (Volume). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_lth_to_exchanges_profit_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_lth_to_exchanges_profit_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 624.3162131362235
  }
]

Long-Term Holder Position Change

get

The monthly net position change of long term holders, i.e. the 30 day change in supply held by long term holders. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nThis is the Point-in-Time (PiT) variant of Long-Term Holder Position Change. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/lth_net_change_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/lth_net_change_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 258218.41955974698
  }
]

Long-Term Holder Supply

get

The total amount of circulating supply held by long term holders. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nThis is the Point-in-Time (PiT) variant of Long-Term Holder Supply. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/lth_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/lth_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 14163502.32150867
  }
]

Long-Term Holder Supply in Loss

get

The total amount of circulating supply that is currently at loss and held by long term holders. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nThis is the Point-in-Time (PiT) variant of Long-Term Holder Supply in Loss. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/lth_loss_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/lth_loss_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 917938.5027314052
  }
]

Long-Term Holder Supply in Profit

get

The total amount of circulating supply that is currently in profit and held by long term holders. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nThis is the Point-in-Time (PiT) variant of Long-Term Holder Supply in Profit. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/lth_profit_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/lth_profit_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 13245563.817831533
  }
]

Long-Term Holder to Exchanges (Volume)

get

The total amount of coins transferred from long-term holders to exchange wallets. Only direct transfers are counted. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Long-Term Holder to Exchanges (Volume). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_lth_to_exchanges_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_lth_to_exchanges_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 679.0872945046451
  }
]

LTH/STH Transfer Volume in Profit/Loss to Exchanges

get

The relative amount of coins moved by by long- and short-term holders in profit/loss to exchanges. Only direct transfers are counted. Coins are considered to be in profit/loss when the price at the time the coins are spent is higher/lower than the entity's average on-chain acquisition price for its funds. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of LTH/STH Transfer Volume in Profit/Loss to Exchanges. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_lth_sth_to_exchanges_profit_loss_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_lth_sth_to_exchanges_profit_loss_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "lth_loss": 0.0018559673335949564,
      "lth_profit": 0.021155516167745293,
      "sth_loss": 0.17986273660779664,
      "sth_profit": 0.7971257798908631
    }
  }
]

Miner Balance

get

The total supply held in miner addresses.\n\nThis is the Point-in-Time (PiT) variant of Miner Balance. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

minerstringRequired

miner name (see /v1/metrics/distribution/balance_miners_sum_pit/miners for a full list)

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/distribution/balance_miners_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/distribution/balance_miners_sum_pit?a=text&miner=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 1096203.7201267101
  }
]

Miner Balance (Stacked)

get

The total supply held in miner addresses.\n\nThis is the Point-in-Time (PiT) variant of Miner Balance (Stacked). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/distribution/balance_miners_all_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/distribution/balance_miners_all_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "balances": {
      "1THash&58COIN": 0.00028064,
      "AntPool": 277.07440821,
      "ArkPool": 0.36334259,
      "BTC.TOP": 0,
      "BTC.com": 41.12040585,
      "BinancePool": 41945.9970803,
      "BitFury": 0.04321233,
      "BitMinter": 0.00007497,
      "Bixin": 69.23008853,
      "DPool": 0,
      "F2Pool": 534.98958239,
      "FoundryUSAPool": 1151.50222133,
      "Genesis": 100.16062095000001,
      "HuobiPool": 0.00220738,
      "KuCoinPool": 0.00005888,
      "Lubian.com": 14139.291815370001,
      "LuxorTech": 140.96416157000002,
      "MaraPool": 3957.3827397600003,
      "NovaBlock": 0,
      "OKExPool": 0.00014476,
      "Patoshi": 1096203.7201267101,
      "PegaPool": 0,
      "Poolin": 876.1037991100001,
      "SBICrypto": 266.64516334,
      "SigmaPool": 45.305849970000004,
      "SlushPool": 93.4127328,
      "SpiderPool": 82.73571534,
      "TerraPool": 0.00017293,
      "UKRPool": 0,
      "Ultimus": 15.83261094,
      "ViaBTC": 54.43525442,
      "other": 640395.81862662
    }
  }
]

Miner Incoming Transfers

get

The total number of transfers in which the receiver is a miners' address.\n\nThis is the Point-in-Time (PiT) variant of Miner Incoming Transfers. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

minerstringRequired

miner name (see /v1/metrics/transactions/transfers_to_miners_count_pit/miners for a full list)

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_to_miners_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_to_miners_count_pit?a=text&miner=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0
  }
]

Miner Inflow Volume

get

The total amount of coins transferred to miner addresses.\n\nThis is the Point-in-Time (PiT) variant of Miner Inflow Volume. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

minerstringRequired

miner name (see /v1/metrics/transactions/transfers_volume_to_miners_sum_pit/miners for a full list)

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_to_miners_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_to_miners_sum_pit?a=text&miner=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0
  }
]

Miner Net Position Change

get

The 30d change of the supply held in miner addresses.\n\nThis is the Point-in-Time (PiT) variant of Miner Net Position Change. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/distribution/balance_miners_change_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/distribution/balance_miners_change_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.00037492020055651665
  }
]

Miner Netflow Volume

get

The difference between miner's inflow and outflow, i.e the net flow of coins into/out of miner addresses.\n\nThis is the Point-in-Time (PiT) variant of Miner Netflow Volume. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

minerstringRequired

miner name (see /v1/metrics/transactions/transfers_volume_miners_net_pit/miners for a full list)

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_miners_net_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_miners_net_pit?a=text&miner=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0
  }
]

Miner Outflow Volume

get

The total amount of coins transferred from miner addresses.\n\nThis is the Point-in-Time (PiT) variant of Miner Outflow Volume. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

minerstringRequired

miner name (see /v1/metrics/transactions/transfers_volume_from_miners_sum_pit/miners for a full list)

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_from_miners_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_from_miners_sum_pit?a=text&miner=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0
  }
]

Miner Outgoing Transfers

get

The total number of transfers in which the sender is a miners' address.\n\nThis is the Point-in-Time (PiT) variant of Miner Outgoing Transfers. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

minerstringRequired

miner name (see /v1/metrics/transactions/transfers_from_miners_count_pit/miners for a full list)

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_from_miners_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_from_miners_count_pit?a=text&miner=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0
  }
]

Miner Revenue (Block Rewards)

get

The total amount of newly minted coins, i.e. block rewards.\n\nThis is the Point-in-Time (PiT) variant of Miner Revenue (Block Rewards). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

minerstringRequired

miner name (see /v1/metrics/mining/volume_mined_sum_pit/miners for a full list)

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/mining/volume_mined_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/mining/volume_mined_sum_pit?a=text&miner=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0
  }
]

Miner Revenue (Total)

get

The total miner revenue, i.e. fees plus newly minted coins.\n\nThis is the Point-in-Time (PiT) variant of Miner Revenue (Total). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

minerstringRequired

miner name (see /v1/metrics/mining/revenue_sum_pit/miners for a full list)

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/mining/revenue_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/mining/revenue_sum_pit?a=text&miner=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0
  }
]

Miners to Exchanges

get

The total amount of coins transferred from miners to exchange wallets. Only direct transfers are counted. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Miners to Exchanges. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_miners_to_exchanges_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_miners_to_exchanges_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 11.9920544621754
  }
]

Miners to Exchanges (Stacked)

get

The total amount of coins transferred from miners to exchange wallets. Only direct transfers are counted. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Miners to Exchanges (Stacked). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_miners_to_exchanges_all_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_miners_to_exchanges_all_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "volumes": {
      "1THash&58COIN": 0,
      "AntPool": 0,
      "BTC.TOP": 0,
      "BTC.com": 11.9920544621754,
      "BinancePool": 0,
      "Bixin": 0,
      "F2Pool": 5.45013413706833,
      "FoundryUSAPool": 36.71466241,
      "HuobiPool": 0,
      "KuCoinPool": 0,
      "LuxorTech": 0,
      "NovaBlock": 0,
      "OKExPool": 0,
      "PegaPool": 0,
      "Poolin": 0,
      "SBICrypto": 0,
      "SigmaPool": 0.09204493,
      "SlushPool": 3.4509614159165802,
      "SpiderPool": 0,
      "TerraPool": 0,
      "UKRPool": 0,
      "Ultimus": 0,
      "other": 0
    }
  }
]

Mt. Gox Balance

get

The Mt. Gox Trustee Balance corresponds to the amount of BTC held in addresses controlled by Nobuaki Kobayashi, the trustee overseeing the Mt. Gox civil rehabilitation proceedings.\n\nThis is the Point-in-Time (PiT) variant of Mt. Gox Balance. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/distribution/balance_mtgox_trustee_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/distribution/balance_mtgox_trustee_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 32371.44749526
  }
]

New Entities

get

The number of unique entities that appeared for the first time in a transaction of the native coin in the network. Entities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThe computation of this metric requires statistical information from several days, and is therefore only available with a lag of one week.\n\nThis is the Point-in-Time (PiT) variant of New Entities. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/new_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/new_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 88002
  }
]

NFTs Transactions (Absolute)

get

The number of transactions (transaction count) in the Ethereum network by transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\n\nThis is the Point-in-Time (PiT) variant of NFTs Transactions (Absolute). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_count_nfts_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_count_nfts_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "blur.io": 1604,
      "cryptokitties": 1,
      "looksrare": 86,
      "opensea": 457,
      "other_nft_transactions": 5723,
      "rarible": 13,
      "superrare": 67
    }
  }
]

NFTs Transactions (Relative)

get

The relative amount (share) of transactions in the Ethereum network by transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\n\nThis is the Point-in-Time (PiT) variant of NFTs Transactions (Relative). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_count_nfts_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_count_nfts_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "blur.io": 0.20173563073827191,
      "cryptokitties": 0.00012577034335303736,
      "looksrare": 0.010816249528361212,
      "opensea": 0.05747704691233807,
      "other_nft_transactions": 0.7197836750094327,
      "rarible": 0.0016350144635894855,
      "superrare": 0.008426613004653503
    }
  }
]

Number of Whales

get

The number of unique entities holding at least 1k coins.Entities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Number of Whales. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/min_1k_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/min_1k_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 1649
  }
]

OTC Desks Holdings

get

The total amount of coins held on OTC desk addresses. This data is based on three different OTC desks. Note that OTC metrics are based on our labeled data that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of OTC Desks Holdings. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/distribution/balance_otc_desks_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/distribution/balance_otc_desks_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 3986.16156168
  }
]

OTC Desks Incoming Transactions

get

The total count of transfers to OTC desk addresses. This data is based on three different OTC desks. Note that OTC metrics are based on our labeled data that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of OTC Desks Incoming Transactions. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_to_otc_desks_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_to_otc_desks_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 55
  }
]

OTC Desks Inflows

get

The total amount of coins transferred to OTC desk addresses. This data is based on three different OTC desks. Note that OTC metrics are based on our labeled data that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of OTC Desks Inflows. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_to_otc_desks_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_to_otc_desks_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 3302.1664206600003
  }
]

OTC Desks Outflows

get

The total amount of coins transferred from OTC desk addresses. This data is based on three different OTC desks. Note that OTC metrics are based on our labeled data that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of OTC Desks Outflows. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_from_otc_desks_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_from_otc_desks_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 1563.6598624800001
  }
]

OTC Desks Outgoing Transactions

get

The total count of transfers from OTC desk addresses. This data is based on three different OTC desks. Note that OTC metrics are based on our labeled data that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of OTC Desks Outgoing Transactions. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_from_otc_desks_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_from_otc_desks_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 35
  }
]

Percent Entities in Profit

get

The percentage of entities in the network that are currently in profit, e.g. the entities whose funds where on average bought at prices lower than the current price. "Buy price" is here defined as the price at the time coins were transferred into addresses controlled by the entity. Entities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information this article.\n\nThis is the Point-in-Time (PiT) variant of Percent Entities in Profit. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/profit_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/profit_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.912347351201666
  }
]

Receiving Entities

get

The number of unique entities that were active as a receiver. Entities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Receiving Entities. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/receiving_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/receiving_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 179168
  }
]

Relative Long/Short-Term Holder Supply

get

The relative amount of circulating supply of held by long- and short-term holders in profit/loss. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nThis is the Point-in-Time (PiT) variant of Relative Long/Short-Term Holder Supply. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/lth_sth_profit_loss_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/lth_sth_profit_loss_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "lth_loss": 0.05473407199103512,
      "lth_profit": 0.7897954399012458,
      "sth_loss": 0.0633050217917743,
      "sth_profit": 0.09214607787069173
    }
  }
]

Relative LTH/STH Realized Profit/Loss

get

Relative distribution of the total profit and loss (USD value) of all coins moved by long- and short-term holders. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Relative LTH/STH Realized Profit/Loss. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/realized_profit_loss_lth_sth_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/realized_profit_loss_lth_sth_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "lth_realized_loss": 0.0025802653168425617,
      "lth_realized_profit": 0.7234436560134411,
      "sth_realized_loss": 0.01003106730638534,
      "sth_realized_profit": 0.2639450113633311
    }
  }
]

Relative LTH/STH Realized Profit/Loss to Exchanges

get

Relative distribution of the total profit and loss (USD value) of all coins moved by long- and short-term holders to exchanges. Realized profit/loss denotes the total profit/loss (in USD) of all moved coins whose price at their last movement was lower/higher than the price at the current movement. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Relative LTH/STH Realized Profit/Loss to Exchanges. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/indicators/realized_profit_loss_lth_sth_to_exchanges_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/indicators/realized_profit_loss_lth_sth_to_exchanges_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "lth_realized_loss": 0.0026132290682245748,
      "lth_realized_profit": 0.1854513065477442,
      "sth_realized_loss": 0.021710480870103643,
      "sth_realized_profit": 0.7902249835139277
    }
  }
]

Relative Transfer Volume by Size (Entity-Adjusted)

get

Entity-adjusted relative on-chain volume breakdown by the USD value of the transfers.\n\nThis is the Point-in-Time (PiT) variant of Relative Transfer Volume by Size (Entity-Adjusted). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_by_size_entity_adjusted_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_by_size_entity_adjusted_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "vol_0_to_1k": 0.005112523119398073,
      "vol_100k_to_1m": 0.11292053695909048,
      "vol_10k_to_100k": 0.041922628330286406,
      "vol_10m_plus": 0.663906963929161,
      "vol_1k_to_10k": 0.01238921608899927,
      "vol_1m_to_10m": 0.16374813157306206
    }
  }
]

Sending Entities

get

The number of unique entities that were active as a sender. Entities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nThis is the Point-in-Time (PiT) variant of Sending Entities. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/sending_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/sending_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 120383
  }
]

Short-Term Holder in Loss to Exchanges (Volume)

get

The total amount of coins transferred from short-term holders in loss to exchange wallets. Only direct transfers are counted. Coins are considered to be in loss when the price at the time the coins are spent is lower than the entity's average on-chain acquisition price for its funds. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Short-Term Holder in Loss to Exchanges (Volume). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_sth_to_exchanges_loss_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_sth_to_exchanges_loss_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 5307.893303709703
  }
]

Short-Term Holder in Profit to Exchanges (Volume)

get

The total amount of coins transferred from short-term holders in profit to exchange wallets. Only direct transfers are counted. Coins are considered to be in profit when the price at the time the coins are spent is higher than the entity's average on-chain acquisition price for its funds. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Short-Term Holder in Profit to Exchanges (Volume). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_sth_to_exchanges_profit_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_sth_to_exchanges_profit_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 23523.81971438146
  }
]

Short-Term Holder Profit/Loss Ratio

get

The ratio of the Short-Term Holder Supply in Profit and the Short-Term Holder Supply in Loss. Similar to SOPR, it detects local bottoms in bull markets and local tops in bear markets. This metric was first put forward by ARK Invest.\n\nThis is the Point-in-Time (PiT) variant of Short-Term Holder Profit/Loss Ratio. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/sth_profit_loss_ratio_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/sth_profit_loss_ratio_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 1.4555887552457165
  }
]

Short-Term Holder Supply

get

The total amount of circulating supply held by short term holders. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nThis is the Point-in-Time (PiT) variant of Short-Term Holder Supply. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/sth_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/sth_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 2607376.7550883386
  }
]

Short-Term Holder Supply in Loss

get

The total amount of circulating supply that is currently at loss and held by short term holders. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nThis is the Point-in-Time (PiT) variant of Short-Term Holder Supply in Loss. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/sth_loss_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/sth_loss_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 1061680.8654111854
  }
]

Short-Term Holder Supply in Profit

get

The total amount of circulating supply that is currently in profit and held by short term holders. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nThis is the Point-in-Time (PiT) variant of Short-Term Holder Supply in Profit. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/sth_profit_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/sth_profit_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 1545370.7293520626
  }
]

Short-Term Holder to Exchanges (Volume)

get

The total amount of coins transferred from short-term holders to exchange wallets. Only direct transfers are counted. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nEntities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see this article.\n\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Short-Term Holder to Exchanges (Volume). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_sth_to_exchanges_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_sth_to_exchanges_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 28831.713018091163
  }
]

Stablecoins Transactions (Absolute)

get

The number of transactions (transaction count) in the Ethereum network by stablecoin transactions. Stablecoin are fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\n\nThis is the Point-in-Time (PiT) variant of Stablecoins Transactions (Absolute). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_count_stablecoins_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_count_stablecoins_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "busd": 19,
      "dai": 1958,
      "gusd": 15,
      "other_stablecoins": 927,
      "sai": 1,
      "tusd": 46,
      "usda": null,
      "usdc": 31705,
      "usdp": 63,
      "usdt": 102879,
      "ust": 6
    }
  }
]

Stablecoins Transactions (Relative)

get

The relative amount (share) of transactions in the Ethereum network by stablecoin transactions. Stablecoin are fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\n\nThis is the Point-in-Time (PiT) variant of Stablecoins Transactions (Relative). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_count_stablecoins_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_count_stablecoins_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "busd": 0.00013806233150945728,
      "dai": 0.014227686583974596,
      "gusd": 0.00010899657750746627,
      "other_stablecoins": 0.006735988489961415,
      "sai": 0.000007266438500497751,
      "tusd": 0.00033425617102289653,
      "usda": null,
      "usdc": 0.2303824326582812,
      "usdp": 0.0004577856255313583,
      "usdt": 0.7475639264927081,
      "ust": 0.00004359863100298651
    }
  }
]

Supply Held by Entities with Balance < 0.001

get

The total circulating supply held by entities with balance lower than 0.001 coins.\n\nThis is the Point-in-Time (PiT) variant of Supply Held by Entities with Balance < 0.001. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/supply_balance_less_0001_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/supply_balance_less_0001_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 5105.60783652
  }
]

Supply Held by Entities with Balance > 100k

get

The total circulating supply held by entities with balance of at least 100,000 coins.\n\nThis is the Point-in-Time (PiT) variant of Supply Held by Entities with Balance > 100k. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/supply_balance_more_100k_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/supply_balance_more_100k_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 4313774.7189982105
  }
]

Supply Held by Entities with Balance 0.001 - 0.01

get

The total circulating supply held by entities with balance between 0.001 and 0.01 coins.\n\nThis is the Point-in-Time (PiT) variant of Supply Held by Entities with Balance 0.001 - 0.01. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/supply_balance_0001_001_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/supply_balance_0001_001_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 40365.93479589
  }
]

Supply Held by Entities with Balance 0.01 - 0.1

get

The total circulating supply held by entities with balance between 0.01 and 0.1 coins.\n\nThis is the Point-in-Time (PiT) variant of Supply Held by Entities with Balance 0.01 - 0.1. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/supply_balance_001_01_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/supply_balance_001_01_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 262889.20938295
  }
]

Supply Held by Entities with Balance 0.1 - 1

get

The total circulating supply held by entities with balance between 0.1 and 1 coins.\n\nThis is the Point-in-Time (PiT) variant of Supply Held by Entities with Balance 0.1 - 1. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/supply_balance_01_1_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/supply_balance_01_1_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 1076183.00720873
  }
]

Supply Held by Entities with Balance 1 - 10

get

The total circulating supply held by entities with balance between 1 and 10 coins.\n\nThis is the Point-in-Time (PiT) variant of Supply Held by Entities with Balance 1 - 10. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/supply_balance_1_10_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/supply_balance_1_10_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 2119255.1097222
  }
]

Supply Held by Entities with Balance 10 - 100

get

The total circulating supply held by entities with balance between 10 and 100 coins.\n\nThis is the Point-in-Time (PiT) variant of Supply Held by Entities with Balance 10 - 100. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/supply_balance_10_100_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/supply_balance_10_100_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 3234023.80017155
  }
]

Supply Held by Entities with Balance 100 - 1k

get

The total circulating supply held by entities with balance between 100 and 1,000 coins.\n\nThis is the Point-in-Time (PiT) variant of Supply Held by Entities with Balance 100 - 1k. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/supply_balance_100_1k_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/supply_balance_100_1k_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 3725895.93570727
  }
]

Supply Held by Entities with Balance 10k - 100k

get

The total circulating supply held by entities with balance between 10,000 and 100,000 coins.\n\nThis is the Point-in-Time (PiT) variant of Supply Held by Entities with Balance 10k - 100k. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/supply_balance_10k_100k_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/supply_balance_10k_100k_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 1602489.0545491
  }
]

Supply Held by Entities with Balance 1k - 10k

get

The total circulating supply held by entities with balance between 1,000 and 10,000 coins.\n\nThis is the Point-in-Time (PiT) variant of Supply Held by Entities with Balance 1k - 10k. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/entities/supply_balance_1k_10k_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/entities/supply_balance_1k_10k_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 3380424.53892235
  }
]

Supply in Smart Contracts

get

The percent of total supply of the token that is held in smart contracts.\n\nThis is the Point-in-Time (PiT) variant of Supply in Smart Contracts. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/distribution/supply_contracts_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/distribution/supply_contracts_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.42262716495709357
  }
]

Supply of Top 1% Addresses

get

The percentage of supply held by the top 1% addresses. Exchange addresses, smart contract addresses, and other special asset-specific addresses (e.g. team fund addresses) are excluded.\n\nThis is the Point-in-Time (PiT) variant of Supply of Top 1% Addresses. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/distribution/balance_1pct_holders_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/distribution/balance_1pct_holders_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 0.9638277567569968
  }
]

Total Transfer Volume by Size (Entity-Adjusted)

get

Entity-adjusted on-chain volume breakdown by the USD value of the transfers.\n\nThis is the Point-in-Time (PiT) variant of Total Transfer Volume by Size (Entity-Adjusted). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_by_size_entity_adjusted_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_by_size_entity_adjusted_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "vol_0_to_1k": 64495095.05984042,
      "vol_100k_to_1m": 1424506177.3416903,
      "vol_10k_to_100k": 528859006.8299809,
      "vol_10m_plus": 8375266331.224451,
      "vol_1k_to_10k": 156291453.4987938,
      "vol_1m_to_10m": 2065702406.6268272
    }
  }
]

Transaction Type Breakdown (Absolute)

get

The number of transactions (transaction count) in the Ethereum network by category. Transactions are classified into the following categories:\n\n- Vanilla: Pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\n\n- ERC20: All transactions calling ERC20 contracts. Contracts in the Stablecoins category are excluded here.\n\n- Stablecoins: Fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\n\n- DeFi: On-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs). We include over 90+ DeFi protocols in this category, such as Uniswap, Etherdelta, 1inch, Sushiswap, Aave, and 0x.\n\n- Bridges: Contracts allowing transfer of tokens between different blockchains. We include 50+ bridges in this category, such as Ronin, Polygon, Optimism, and Arbitrum.\n\n- NFTs: Transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\n\n- MEV Bots: Miner Extractable Value (MEV) bots execute transactions for profit by reordering, inserting, and censoring transactions within blocks.\n\n- Other: This category includes all other transactions in the Ethereum network that are not included in categories listed above.\n\nThis is the Point-in-Time (PiT) variant of Transaction Type Breakdown (Absolute). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/tx_types_breakdown_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/tx_types_breakdown_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "bridge": 4032,
      "defi": 180194,
      "erc20": 167041,
      "mev-bot": 4982,
      "nft_transfer": 7898,
      "other": 295187,
      "stablecoin": 137619,
      "vanilla": 359872
    }
  }
]

Transaction Type Breakdown (Relative)

get

The relative amount (share) of transactions in the Ethereum network by category. Transactions are classified into one of the following categories:\n\n- Vanilla: Pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\n\n- ERC20: All transactions calling ERC20 contracts. Contracts in the Stablecoins category are excluded here.\n\n- Stablecoins: Fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\n\n- DeFi: On-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs). We include over 90+ DeFi protocols in this category, such as Uniswap, Etherdelta, 1inch, Sushiswap, Aave, and 0x.\n\n- Bridges: Contracts allowing transfer of tokens between different blockchains. We include 50+ bridges in this category, such as Ronin, Polygon, Optimism, and Arbitrum.\n\n- NFTs: Transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\n\n- MEV Bots: Miner Extractable Value (MEV) bots execute transactions for profit by reordering, inserting, and censoring transactions within blocks.\n\n- Other: This category includes all other transactions in the Ethereum network that are not included in categories listed above.\n\nThis is the Point-in-Time (PiT) variant of Transaction Type Breakdown (Relative). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/tx_types_breakdown_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/tx_types_breakdown_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "bridge": 0.00348540185421304,
      "defi": 0.1557659974499168,
      "erc20": 0.14439608410952393,
      "mev-bot": 0.00430661508871264,
      "nft_transfer": 0.006827307501134571,
      "other": 0.25516996952866683,
      "stablecoin": 0.11896267801957945,
      "vanilla": 0.31108594644825277
    }
  }
]

US Government Balance

get

The US Government Balance corresponds to the amount of BTC held in addresses controlled by US authorities. The metric includes seized funds, e.g. from the 2016 Bitfinex Hack or the 2012 Silk Road Hack. We constantly keep updating the set of addresses contributing to the total balance.\n\nThis is the Point-in-Time (PiT) variant of US Government Balance. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/distribution/balance_us_government_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/distribution/balance_us_government_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 197236.67965722
  }
]

US Year-over-Year Supply Change

get

\nThis metric aims at giving an estimate for the year-over-year change in the share of the Bitcoin supply to be held/traded in the US.\n\nGeolocation of Bitcoin supply is performed probabilistically at the entity level. The timestamps of all transactions created by an entity are correlated with the working hours of different geographical regions to determine the probabilities for each entity being located in the US, Europe, or Asia. Working hours are defined as:\n\n* US: 8am to 8pm Eastern Time (13:00-01:00 UTC)\n* EU: 8am to 8pm Central European Time (07:00-19:00 UTC)\n* Asia: 8am to 8pm China Standard Time (00:00-12:00 UTC)\n\nAn entity's balance will only contribute to the supply in the respective region if the location can be determined with a high certainty. Supply held on exchanges wallets are excluded.\n \n\nThis is the Point-in-Time (PiT) variant of US Year-over-Year Supply Change. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/supply/amer_1y_supply_change_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/supply/amer_1y_supply_change_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": -0.07104815430441169
  }
]

Vanilla Transactions (Absolute)

get

The amount of gas consumed by the Ethereum network by vanilla transactions. Vanilla transactions are pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\n If at least one of the EOAs participating in the transaction (the receiver, the sender, or both) belongs to an exchange, the amount will be represented in the exchange cohort.\n Note that occasionally the value of the last datapoint can slightly change as some addresses initially transact as "vanilla" before their associated smart contract deployment is observed.\n\nThis is the Point-in-Time (PiT) variant of Vanilla Transactions (Absolute). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_count_vanilla_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_count_vanilla_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "exchange": 63798,
      "vanilla": 301402
    }
  }
]

Vanilla Transactions (Relative)

get

The relative amount (share) of gas consumed by the Ethereum network by vanilla transactions. Vanilla transactions are pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\n If at least one of the EOAs participating in the transaction (the receiver, the sender, or both) belongs to an exchange, the amount will be represented in the exchange cohort.\n Note that occasionally the value of the last datapoint can slightly change as some addresses initially transact as "vanilla" before their associated smart contract deployment is observed.\n\nThis is the Point-in-Time (PiT) variant of Vanilla Transactions (Relative). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - ETH

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_count_vanilla_relative_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_count_vanilla_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "o": {
      "exchange": 0.1746933187294633,
      "vanilla": 0.8253066812705367
    }
  }
]

Wrapped BTC (WBTC) Balance

get

Wrapped Bitcoin (WBTC) is the first ERC20 token backed 1:1 with Bitcoin and designed to act as representation of Bitcoin on the Ethereum blockchain. The WBTC supply listed here corresponds to the amount of Bitcoin held by BitGo, the custodian responsible for minting new WBTC ERC20 tokens and guaranteeing backing of new ERC20 tokens by actual BTC.\n\nThis is the Point-in-Time (PiT) variant of Wrapped BTC (WBTC) Balance. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/distribution/balance_wbtc_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/distribution/balance_wbtc_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 152958.34122995
  }
]

Whale Deposits to Exchanges (Counts)

get

The total count of transfers from whales to exchange addresses. Whales are defined as network entities (cluster of addresses) that hold at least 1,000 BTC. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Whale Deposits to Exchanges (Counts). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_whales_to_exchanges_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_whales_to_exchanges_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 4783
  }
]

Whale Deposits to Exchanges (Volume)

get

The total amount of coins transferred from whales to exchange wallets. Only direct transfers are counted. Whales are defined as network entities (cluster of addresses) that hold at least 1,000 BTC. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Whale Deposits to Exchanges (Volume). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_whales_to_exchanges_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_whales_to_exchanges_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 11086.975323385812
  }
]

Whale Withdrawals from Exchanges (Counts)

get

The total count of transfers from exchange addresses to whales. Whales are defined as network entities (cluster of addresses) that hold at least 1,000 BTC. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Whale Withdrawals from Exchanges (Counts). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_exchanges_to_whales_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_exchanges_to_whales_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 2197
  }
]

Whale Withdrawals from Exchanges (Volume)

get

The total amount of coins transferred from exchange wallets to whale entities. Only direct transfers are counted. Whales are defined as network entities (cluster of addresses) that hold at least 1,000 BTC. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of Whale Withdrawals from Exchanges (Volume). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id - BTC

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

cstringOptional

currency - NATIVE, USD

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/transactions/transfers_volume_exchanges_to_whales_sum_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/transactions/transfers_volume_exchanges_to_whales_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 11185.609478787092
  }
]

Withdrawing Addresses

get

The number of unique addresses that appeared as a receiver in a transaction receiving funds from an exchanges.\n\nThis is the Point-in-Time (PiT) variant of Withdrawing Addresses. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.

View in Studio

Authorizations

ApiKeyAuth

api_keystringRequired

Your Glassnode API key

Query parameters

astringRequired

asset id (see list below for more details)

sintegerOptional

since, unix timestamp

uintegerOptional

until, unix timestamp

istringOptional

frequency interval - 10m, 1h, 1month, 1w, 24h

fstring · enumOptional

format - csv, json

Default: jsonPossible values:

timestamp_formatstring · enumOptional

timestamp format - unix or humanized (RFC 3339)

Default: unixPossible values:

Responses

200

Successful response

application/json

400

Bad Request - Invalid parameters or unsupported asset

application/json

401

Unauthorized - Invalid or missing API key

application/json

429

Too Many Requests - Rate limit exceeded

application/json

get

/v1/metrics/addresses/receiving_from_exchanges_count_pit

HTTPcURLJavaScriptPython

GET /v1/metrics/addresses/receiving_from_exchanges_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*

[
  {
    "t": 1726790400,
    "v": 26940
  }
]