Transactions
Last updated
Last updated
Definition
The count of all transactions within the most recent block processed.
Dictionary
Name | MetricID | Unit | Interval |
---|---|---|---|
Transactions in Block | block_tx_count | Count of transactions | 1b |
Methodology
The most recent block we processed within a 1-minute window is evaluated and the number of transactions within the block are counted. For UTXO based currencies, this includes the coinbase transaction.
Available Assets
Bitcoin (BTC), Ethereum (ETH)
Sample Query
Definition
The count of all mempool transactions at a point in time.
Dictionary
Name | MetricID | Unit | Interval |
---|---|---|---|
Mempool Transaction Count | mempool_count | Transaction | 1m |
Methodology
The mempool is evaluated and all transactions indexed. All unprocessed mempool transactions at a point in time are then counted.
Available Assets
Bitcoin (BTC)
Sample Query
Definition
The count of all transactions that have entered the mempool over the course of a 1-minute aggregation window. The beginning of this time window is noted in the “time” field of the response.
Dictionary
Name | MetricID | Unit | Interval |
---|---|---|---|
Transaction Count entered mempool 1 minute | mempool_count_entered_1m | Transaction | 1m |
Methodology
The mempool is evaluated and all transactions that have been entered (new transactions broadcasted by users) since a point in time are counted.
Available Assets
Bitcoin (BTC)
Sample Query
Transactions metrics can be accessed using these endpoints:
timeseries/asset-metrics
and by passing in the metric ID's block_tx_count*
and mempool_count_*
in the metrics
parameter.
Returns requested metrics for specified assets. Results for block by block metrics (1b
frequency) are ordered by tuple (asset, height, block_hash)
, all other metrics are ordered by tuple (asset, time)
. You can change the sorting using sort
query parameter. Supported output formats are json
(default) and csv
, use format
query parameter to override it. To fetch the next page of results use next_page_url
JSON response field or x-next-page-url
CSV HTTP header if present. If multiple metrics are requested in the same time the strict policy for partially available metrics among requested ones is applied:
Time series of metrics for an asset.
Token of the next page results for a given request.
URL of the next page results for a given request.