Blockchair Updates

Enhancements to the Bitcoin-like and Ethereum-like dashboards

• New hashrate dashboard for all Bitcoin-like and Ethereum-like chains: https://api.blockchair.com/{:chain}/dashboards/hashrate that outputs the estimated hashrate by day. Example: https://api.blockchair.com/bitcoin/dashboards/hashrate.
• New difficulty dashboard for Bitcoin: https://api.blockchair.com/bitcoin/dashboards/difficulty. It outputs:
  • All completed difficulty "periods" (2016 blocks each). status is completed, hashrate is the estimated average hashrate within the period, avg_block_time is the average time between blocks in seconds
  • The current difficulty period. status is ongoing
  • The next difficulty period. status is planned, start_time is the estimated time when the period will start based on the current hashrate and the number of blocks left in the current period, difficulty is the estimated difficulty for the next period, hashrate is the same as for the current period, avg_block_time is always 600 (10 minutes) as it's the target time between blocks

Enhancements to the Bitcoin-like and Ethereum-like dashboards

• Enhancements to the Ethereum transaction dashboard (https://api.blockchair.com/{:eth_chain}/dashboards/transaction/{:hash}) for unconfirmed transactions. Please note that these values are not final and may change as transactions get confirmed: tracing unconfirmed transactions doesn't take possible changes to the state into account.
  • If the ?events=true option is used, API returns values for gas_used, fee, fee_usd instead of nulls
  • If the ?trace_mempool=true option is used, API returns values for internal_value and internal_value_usd instead of nulls
  • API still always returns null for failed

• There's a new option for the Ethereum address dashboard (https://api.blockchair.com/{:eth_chain}/dashboards/address/{:address}): ?transactions_instead_of_calls=true. If applied, it returns the list of latest transaction hashes in the transactions array instead of returning the calls array. An important difference is that ERC-20 transfers that weren't previously included in the calls array will be among transactions. This option also affects transaction_count behaviour: if enabled, it returns the transaction count for an address which takes ERC-20 transfers into account. Using this option costs 2. The option has no effect on contracts (i.e. for contracts the calls array will be returned even if the option is enabled).
• The Ethereum stats dashboard (https://api.blockchair.com/{:eth_chain}/stats) now also outputs addresses yielding the total number of addresses (including both accounts and contracts) ever seen on chain.

We have added support for the London hard fork to our API!

• Added support for the Ethereum London hard fork. New table fields (for Ethereum and Ethereum Goerli Testnet):
  • Blocks:
    • base_fee_per_gas (queryable, sortable, aggregatable). Average base fee per day example: https://api.blockchair.com/ethereum/blocks?a=date,avg(base_fee_per_gas)&q=id(12965000..)
    • burned_total (queryable, sortable, aggregatable). Examples:
      • Total ETH burned: https://api.blockchair.com/ethereum/blocks?a=date,sum(burned_total)&q=id(12965000..)
      • Burned to minted ratio by day: https://api.blockchair.com/ethereum/blocks?a=date,f(sum(burned_total)/sum(generation))&q=id(12965000..)
  • Uncles:
    • base_fee_per_gas (queryable, sortable, aggregatable)
  • Transactions:
    • effective_gas_price (queryable, sortable, aggregatable)
    • max_fee_per_gas (null for legacy transactions; queryable, sortable, aggregatable)
    • max_priority_fee_per_gas (null for legacy transactions; queryable, sortable, aggregatable)
    • base_fee_per_gas (base fee of the block; queryable, sortable, aggregatable)
    • burned (calculated as gas_used * base_fee_per_gas; queryable, sortable, aggregatable)
• Added burned and burned_24h to the https://api.blockchair.com/{:eth_chain}/stats dashboard
• Added version field (queryable, aggregatable) to Ethereum transactions. 0 represents legacy transactions, 1 is for EIP-2718 transactions, 2 is for London transactions. In Ethereum terminology this is "type" instead of "version", but as we're already using "type" for another column, we decided to go with "version". Example: https://api.blockchair.com/ethereum/transactions?a=version,count()&q=block_id(12965000..). Please note that for all transactions before block #12965000 it always returns 0, even for EIP-2718 transactions: this will be fixed in one of the next updates.
• Added support for the Ethereum Berlin hard fork. Transactions now have an additional field called type_2718 (queryable) that represents transaction type as outlined in EIP-2718