circle-info
Work directly with Glassnode engineers to solve integration and data challenges.
Request a quote from Glassnode Expert Servicesarrow-up-right
search
WebsiteStudioInsightsTwitter

Point-In-Time

hashtag
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 Addressesarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/addresses/accumulation_count_pit

hashtag
Accumulation Balance

get

The total amount of funds held in accumulation addressesarrow-up-right. 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 Balancearrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/addresses/accumulation_balance_pit

hashtag
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 Academyarrow-up-right.\n\nThis is the Point-in-Time (PiT) variant of Accumulation Trend Scorearrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/indicators/accumulation_trend_score_pit

hashtag
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 articlearrow-up-right.\n\nThis is the Point-in-Time (PiT) variant of Active Entitiesarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/entities/active_count_pit

hashtag
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 Changearrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/supply/apac_1y_supply_change_pit

hashtag
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 Chainarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/bridges/deposits_by_chain_pit

hashtag
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 Chainarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/bridges/net_volume_by_chain_pit

hashtag
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)arrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/transactions/transfers_count_bridges_pit

hashtag
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)arrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/transactions/transfers_count_bridges_relative_pit

hashtag
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 TVLarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/bridges/total_value_locked_by_chain_pit

hashtag
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 Relativearrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/bridges/total_value_locked_by_chain_relative_pit

hashtag
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 Chainarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/bridges/withdrawals_by_chain_pit

hashtag
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 Countarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/transactions/transfers_from_coinjoins_count_pit

hashtag
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 Volumearrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/transactions/transfers_volume_from_coinjoins_sum_pit

hashtag
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)arrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/transactions/transfers_count_defi_pit

hashtag
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)arrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/transactions/transfers_count_defi_relative_pit

hashtag
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 Addressesarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/addresses/sending_to_exchanges_count_pit

hashtag
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 Puellarrow-up-right. For more information please read his introductory articlearrow-up-right.\n\nThis is the Point-in-Time (PiT) variant of Dormancy Flowarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/indicators/dormancy_flow_pit

hashtag
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 articlearrow-up-right.\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 Growtharrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/entities/net_growth_count_pit

hashtag
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 Distributionarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/entities/supply_distribution_relative_pit

hashtag
Entity- and Supply-Adjusted CYD

get

Coin Years Destroyed (CYD) is defined as the 365 day rolling sum of Coin Days Destroyed (CDD)arrow-up-right, 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 articlearrow-up-right 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 Investarrow-up-right 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 CYDarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/indicators/cyd_account_based_supply_adjusted_pit

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

get

90D Coin Days Destroyed is the 90 day rolling sum of Coin Days Destroyed (CDD)arrow-up-right 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 articlearrow-up-right 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)arrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/indicators/cdd90_account_based_age_adjusted_pit

hashtag
Entity-Adjusted ASOL

get

Entity-adjusted ASOL is an improved variant of ASOLarrow-up-right 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 articlearrow-up-right.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted ASOLarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/indicators/asol_account_based_pit

hashtag
Entity-Adjusted CDD

get

Entity-adjusted CDD is an improved variant of CDDarrow-up-right 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 articlearrow-up-right.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted CDDarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/indicators/cdd_account_based_pit

hashtag
Entity-Adjusted CYD

get

Coin Years Destroyed (CYD) is defined as the 365 day rolling sum of Coin Days Destroyed (CDD)arrow-up-right, 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 articlearrow-up-right for more information). This metric was first put forward by ARK Investarrow-up-right.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted CYDarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/indicators/cyd_account_based_pit

hashtag
Entity-Adjusted Dormancy

get

Entity-adjusted Dormancy is an improved variant of Average Coin Dormancyarrow-up-right 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 articlearrow-up-right.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Dormancyarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/indicators/dormancy_account_based_pit

hashtag
Entity-Adjusted Liveliness

get

Entity-adjusted Liveliness is an improved variant of Livelinessarrow-up-right 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 articlearrow-up-right.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Livelinessarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/indicators/liveliness_account_based_pit

hashtag
Entity-Adjusted Long-Term Holder ASOL

get

Long-Term Holderarrow-up-right variant of Entity-Adjusted ASOLarrow-up-right. 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 datearrow-up-right 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 articlearrow-up-right.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Long-Term Holder ASOLarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/indicators/asol_lth_account_based_pit

hashtag
Entity-Adjusted Long-Term Holder CDD

get

Long-Term Holderarrow-up-right variant of Entity-Adjusted CDDarrow-up-right. 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 datearrow-up-right 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 articlearrow-up-right.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Long-Term Holder CDDarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/indicators/cdd_lth_account_based_pit

hashtag
Entity-Adjusted Long-Term Holder Dormancy

get

Long-Term Holderarrow-up-right variant of Entity-Adjusted Dormancyarrow-up-right. 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 datearrow-up-right 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 articlearrow-up-right.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Long-Term Holder Dormancyarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/indicators/dormancy_lth_account_based_pit

hashtag
Entity-Adjusted LTH Realized Loss

get

Entity-Adjusted variant of Realized Lossarrow-up-right for Long-Term Holdersarrow-up-right, 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 datearrow-up-right 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 articlearrow-up-right.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH Realized Lossarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/indicators/realized_loss_lth_account_based_pit

hashtag
Entity-Adjusted LTH Realized Loss to Exchanges

get

Entity-Adjusted variant of Realized Lossarrow-up-right for coins that are sent from Long-Term Holdersarrow-up-right 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 datearrow-up-right 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 articlearrow-up-right.\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 Exchangesarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/indicators/realized_loss_lth_to_exchanges_account_based_pit

hashtag
Entity-Adjusted LTH Realized Profit

get

Entity-Adjusted variant of Realized Profitarrow-up-right for Long-Term Holdersarrow-up-right, 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 datearrow-up-right 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 articlearrow-up-right.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH Realized Profitarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/indicators/realized_profit_lth_account_based_pit

hashtag
Entity-Adjusted LTH Realized Profit to Exchanges

get

Entity-Adjusted variant of Realized Profitarrow-up-right for coins that are sent from Long-Term Holdersarrow-up-right 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 datearrow-up-right 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 articlearrow-up-right.\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 Exchangesarrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/indicators/realized_profit_lth_to_exchanges_account_based_pit

hashtag
Entity-Adjusted LTH Transfer Volume

get

The total estimated amount of coins moved by long-term holdersarrow-up-right. 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 datearrow-up-right 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 articlearrow-up-right.\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH Transfer Volumearrow-up-right. 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 metricsarrow-up-right for more information.

View in Studioarrow-up-right

Authorizations
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
chevron-right
200

Successful response

application/json
tinteger · int64Optional

Unix timestamp

Example: 1726790400
vone ofOptional

Metric value (can be number, object, or array depending on the metric)

Example: 822077
numberOptional
or
objectOptional
or
arrayOptional
get
/v1/metrics/transactions/transfers_volume_entity_adjusted_from_lth_sum_pit

hashtag
Entity-Adjusted LTH Transfer Volume in Loss

get