BTC Mempool Statistics
This namespace contains endpoints to retrieve statistics on Memory Pool in Bitcoin network. We provide certain metrics such as transaction count, total transaction size, total transaction fee on memory pool, based on fee range, including aggregated metrics. For more detailed information, please refer to the description of each metric.
Mempool Statistics contains three metrics related to transactions waiting to be confirmed. You can see metrics for the number of transactions, the total amount of fees, and the aggregate size in bytes of transactions. Each metric was calculated based on fee level.
Supported Metrics
tx_count*
The total number of unconfirmed transactions (Number)
total_size
The aggregated size in bytes of transactions (Megabyte)
total_fee
The total fee of unconfirmed transactions (BTC)
(*) Default
Supported Windows
hour, day*
(*) Default
For each API request, include this HTTP header:
Authorization with the Bearer {access_token}. Bearer access token is the type of HTTP Authorization. You have to include access token to the HTTP header and note that leading bearer is required.
You must include your access token in HTTP header in every request you make. The token is unique, issued for each client, and regularly changed(once a year). To obtain an access token, please upgrade your plan to Professional or Premium plan. You'll be able to see your access token on the API tab of your profile page after the subscription.
A metric type derived from statistics. Supported formats are json, csv.
tx_countExample: tx_countCurrently, we support day and hour.
dayExample: dayThis defines the starting time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the earliest time.
20191001T100000This defines the ending time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the latest time.
20191001T103025The maximum number of entries to return before the latest data point (or before to if specified). This field ranges from 1 to 100,000.
100Example: 100A format type about return message type. Supported formats are json, csv.
jsonExample: jsonBTC Mempool Stats by relative fee
curl "https://api.cryptoquant.com/v1/btc/mempool/stats-by-relative-fee?window=day&metric_type=tx_count&limit=2"BTC Mempool Stats by relative fee
{
"status": {
"code": 200,
"message": "success"
},
"result": {
"window": "day",
"data": [
{
"datetime": "2019-10-02",
"metric_type": "tx_count",
"metric_unit": "number",
"result": {
"relative_fee_range_0_1": null,
"relative_fee_range_1_2": null,
"relative_fee_range_2_3": null,
"relative_fee_range_3_4": null,
"relative_fee_range_4_5": null,
"relative_fee_range_5_6": null,
"relative_fee_range_6_7": null,
"relative_fee_range_7_8": null,
"relative_fee_range_8_10": null,
"relative_fee_range_10_12": null,
"relative_fee_range_12_14": null,
"relative_fee_range_14_17": null,
"relative_fee_range_17_20": null,
"relative_fee_range_20_25": null,
"relative_fee_range_25_30": null,
"relative_fee_range_30_40": null,
"relative_fee_range_40_50": null,
"relative_fee_range_50_60": null,
"relative_fee_range_60_70": null,
"relative_fee_range_70_80": null,
"relative_fee_range_80_100": null,
"relative_fee_range_100_120": null,
"relative_fee_range_120_140": null,
"relative_fee_range_140_170": null,
"relative_fee_range_170_200": null,
"relative_fee_range_200_250": null,
"relative_fee_range_250_300": null,
"relative_fee_range_300_400": null,
"relative_fee_range_400_500": null,
"relative_fee_range_500_600": null,
"relative_fee_range_600_700": null,
"relative_fee_range_700_800": null,
"relative_fee_range_800_1000": null,
"relative_fee_range_1000_1200": null,
"relative_fee_range_1200_1400": null,
"relative_fee_range_1400_1700": null,
"relative_fee_range_1700_2000": null,
"relative_fee_range_2000_2500": null,
"relative_fee_range_2500_3000": null,
"relative_fee_range_3000_4000": null,
"relative_fee_range_4000_5000": null,
"relative_fee_range_5000_6000": null,
"relative_fee_range_6000_7000": null,
"relative_fee_range_7000_8000": null,
"relative_fee_range_8000_10000": null,
"relative_fee_range_10000_inf": null
}
}
]
}
}Mempool Statistics contains three metrics related to transactions waiting to be confirmed. You can see metrics for the number of transactions, the total amount of fees, and the aggregate size in bytes of transactions.
Supported Metrics
tx_count*
The average number of unconfirmed transactions in selected time range (Number)
total_size
The average aggregate size in bytes of transactions in selected time range (Megabyte)
total_fee
The average total fee of unconfirmed transactions in selected time range (BTC)
(*) Default
Supported Windows
hour, day*
(*) Default
For each API request, include this HTTP header:
Authorization with the Bearer {access_token}. Bearer access token is the type of HTTP Authorization. You have to include access token to the HTTP header and note that leading bearer is required.
You must include your access token in HTTP header in every request you make. The token is unique, issued for each client, and regularly changed(once a year). To obtain an access token, please upgrade your plan to Professional or Premium plan. You'll be able to see your access token on the API tab of your profile page after the subscription.
A metric type derived from statistics. Supported formats are json, csv.
tx_countExample: tx_countCurrently, we support day and hour.
dayExample: dayThis defines the starting time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the earliest time.
20191001T100000This defines the ending time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the latest time.
20191001T103025The maximum number of entries to return before the latest data point (or before to if specified). This field ranges from 1 to 100,000.
100Example: 100A format type about return message type. Supported formats are json, csv.
jsonExample: jsonBTC Mempool Stats (Sum)
curl "https://api.cryptoquant.com/v1/btc/mempool/stats-in-total?window=day&metric_type=tx_count&limit=2"BTC Mempool Stats (Sum)
{
"status": {
"code": 200,
"message": "success"
},
"result": {
"window": "day",
"data": [
{
"datetime": "2019-10-02",
"metric_type": "tx_count",
"metric_unit": "number",
"result": 0
}
]
}
}Last updated
Was this helpful?