Block Attributes
Last updated
Was this helpful?
Last updated
Was this helpful?
Definition
The base fee of the most recent block processed.
Dictionary
Base Fee for Block
block_base_fee
ETH
1b
Methodology
The most recent block we processed within a 1-minute window is evaluated and its Base Fee captured. The concept of a Base Fee was introduced as part of EIP-1559 and it represents the portion of the total transaction fees that is destroyed and taken out of circulation (i.e. burnt). Ethereum post-1559 requires users to pay for a Base Fee as a prerequisite to include transactions in a block. The Base Fee can go up or down on the basis of the size (in gas units) of the previous block.
Available Assets
Ethereum (ETH)
Sample Query
Definition
The priority fee, or tip, of the most recent block processed.
Dictionary
Priority Fee for Block
block_priority_fee
ETH
1b
Methodology
The most recent block we processed within a 1-minute window is evaluated and its Priority Fee, or tip, is captured. The concept of a Miner Tip was introduced as part of EIP-1559 and it represents the portion of the total transaction fees that rewards miners. This serves as an added incentive so that miners prioritize transactions that have opted-in and paid a tip. The other portion is called the Base Fee, and it is burnt (destroyed) after the transaction is included in a block.
Available Assets
Ethereum (ETH)
Sample Query
metrics can be accessed using these endpoints:
timeseries/asset-metrics
and by passing in the metric ID's block_*_fee
in the metrics
parameter.
Returns requested metrics for specified assets.<br/><br/> 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.<br/><br/> Supported output formats are json
(default) and csv
, use format
query parameter to override it.<br/> To fetch the next page of results use next_page_url
JSON response field or x-next-page-url
CSV HTTP header if present.<br/><br/> If multiple metrics are requested in the same time the strict policy for partially available metrics among requested ones is applied: <ul>
/timeseries/asset-metrics
Comma separated list of assets.<br/> Use the /catalog-all/assets endpoint for the full list of supported assets or specify asterisk (*) in order to get metrics for all supported assets.
Comma separated metrics to request time series data for.<br/> Information on all available metrics can be found on page https://docs.coinmetrics.io/info/metrics.<br/> Use the /catalog-all/metrics or /catalog-all/assets endpoint for the full list of supported metrics per asset.
["AdrActCnt","BlkHgt"]
Frequency of the metrics. Supported values are 1b
(block by block), 1s
(one second), 1m
(one minute), 10m
(ten minutes), 1h
(one hour), 1d
(one day), 1d-ny-close
(one day at New York close time). Please refer to the /catalog/metrics
endpoint for the full list.<br/> Use the /catalog-all/assets endpoint for the full list of supported frequencies per asset-metric pair.
1b
Which metric values do you want to see. Applicable only for "reviewable" metrics. You can find them in the /catalog/metrics
endpoint.
all
, flash
, reviewed
, revised
Start of the time interval.<br/> This field refers to the time
field in the response.<br/> Multiple formats of ISO 8601 are supported: 2006-01-20T00:00:00Z
, 2006-01-20T00:00:00.000Z
, 2006-01-20T00:00:00.123456Z
, 2006-01-20T00:00:00.123456789Z
, 2006-01-20
, 20060120
.<br/> Inclusive by default. Mutually exclusive with start_height
and start_hash
.<br/> UTC timezone by default. Z
suffix is optional and timezone
parameter has a priority over it.<br/> If start_time
is omitted, response will include time series from the earliest time available.
End of the time interval.<br/> This field refers to the time
field in the response.<br/> Multiple formats of ISO 8601 are supported: 2006-01-20T00:00:00Z
, 2006-01-20T00:00:00.000Z
, 2006-01-20T00:00:00.123456Z
, 2006-01-20T00:00:00.123456789Z
, 2006-01-20
, 20060120
.<br/> Inclusive by default. Mutually exclusive with end_height
and end_hash
.<br/> UTC timezone by default. Z
suffix is optional and timezone
parameter has a priority over it.<br/> If end_time
is omitted, response will include time series up to the latest time available.
The start height indicates the beginning block height for the set of data that are returned.<br/> Inclusive by default. Mutually exclusive with start_time
and start_hash
.
The end height indicates the ending block height for the set of data that are returned.<br/> Inclusive by default. Mutually exclusive with end_time
and end_hash
.<br/> This parameter is disabled for Community users.
The start hash indicates the beginning block height for the set of data that are returned.<br/> Inclusive by default. Mutually exclusive with start_time
and start_height
.
The end hash indicates the ending block height for the set of data that are returned.<br/> Inclusive by default. Mutually exclusive with end_time
and end_height
.
Inclusive or exclusive corresponding start_*
parameters.
Inclusive or exclusive corresponding end_*
parameters.
Specifies how many blocks behind the chain tip block by block metrics (1b
frequency) are based on. Default for btc
is 2
and 99
for eth
. For example, a min_confirmations
of 0
means metrics are being calculated for the block at the tip of the chain (the latest block received by our node) whereas a min_confirmations
of 6
means that metrics are being applied to the block that is 6
blocks behind the chain tip (i.e., the 7th block if the chain tip is block 1).
Timezone name for start_time
and end_time
timestamps.<br/> This parameter does not modify the output times, which are always UTC
.<br/> Format is defined by TZ database.
America/New_York
Number of items per single page of results.<br/> The value of this parameter is ignored if the endpoint supports the format
parameter and its value is set to json_stream
.
Where does the first page start, at the start of the interval or at the end.
start
, end
How results will be sorted. Metrics with 1b
frequency are sorted by (asset, height, block_hash)
tuples by default. Metrics with other frequencies are sorted by (asset, time)
by default. If you want to sort 1d
metrics by (time, asset)
you should choose time
as value for the sort
parameter.<br/> Sorting by time
is useful if you request metrics for a set of assets.
asset
, height
, time
How many entries per asset result should contain. For example, this combination of parameters assets=btc,eth&metrics=ReferenceRate&limit_per_asset=1
returns the latest ReferenceRate
values for btc
and eth
.
Human-readable formatting of JSON responses.
Format of the response.
json
, csv
Nulls are represented as zeros in the response.
Token for receiving the results from the next page of a query.<br/> Should not be used directly. To iterate through pages just use next_page_url
response field.
Ignore HTTP 403 Forbidden errors
Ignore errors for unsupported assets, metrics or frequencies.