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.

BTC Memory pool Statistics by relative fee range

get

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

Metric Type
Description

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

Supported Windows

hour, day*

(*) Default

Authorizations
AuthorizationstringRequired

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.

Query parameters
metric_typestringOptional

A metric type derived from statistics. Supported formats are json, csv.

Default: tx_countExample: tx_count
windowstringOptional

Currently, we support day and hour.

Default: dayExample: day
fromanyOptional

This 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.

Example: 20191001T100000
toanyOptional

This 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.

Example: 20191001T103025
limitinteger · min: 1 · max: 100000Optional

The maximum number of entries to return before the latest data point (or before to if specified). This field ranges from 1 to 100,000.

Default: 100Example: 100
formatstringOptional

A format type about return message type. Supported formats are json, csv.

Default: jsonExample: json
Responses
chevron-right
200

BTC Mempool Stats by relative fee

application/json
get
/btc/mempool/stats-by-relative-fee
200

BTC Mempool Stats by relative fee

BTC Memory pool Statistics (Sum)

get

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

Metric Type
Description

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

Supported Windows

hour, day*

(*) Default

Authorizations
AuthorizationstringRequired

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.

Query parameters
metric_typestringOptional

A metric type derived from statistics. Supported formats are json, csv.

Default: tx_countExample: tx_count
windowstringOptional

Currently, we support day and hour.

Default: dayExample: day
fromanyOptional

This 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.

Example: 20191001T100000
toanyOptional

This 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.

Example: 20191001T103025
limitinteger · min: 1 · max: 100000Optional

The maximum number of entries to return before the latest data point (or before to if specified). This field ranges from 1 to 100,000.

Default: 100Example: 100
formatstringOptional

A format type about return message type. Supported formats are json, csv.

Default: jsonExample: json
Responses
chevron-right
200

BTC Mempool Stats (Sum)

application/json
get
/btc/mempool/stats-in-total
200

BTC Mempool Stats (Sum)

Last updated

Was this helpful?