Block summaries
Schema
Column Name | Data Type |
---|---|
chain_id | Long |
block_number | Long |
block_timestamp | Long |
hash | String |
canonical_rlp | String |
parent_hash | String |
coinbase | String |
gas_limit | Long |
gas_used | Long |
difficulty | BigDecimal |
nonce | BigDecimal |
txn_count | Long |
uncles | JSON - Array of uncles' hashes |
base_fee_per_gas_gwei | BigDecimal |
mix_hash | String |
epoch | Long - optional |
slot | Long - optional |
proposer_index | Long - optional |
proposer_public_key | String - optional |
excess_blob_gas | BigDecimal - optional |
blob_gas_used | BigDecimal - optional |
Coverage
Ethereum, Base, Arbitrum
Usage notes
The table contains only one row per block number, reorg'd blocks are removed.
Some columns are optional since they contain fields that were added at a later time in the chain. To properly handle null values, pinot suggests usingSET enableNullHandling=true;
before the SQL query. That will enable filtering the null values using theWHERE col IS NULL
predicate and ignore null values in aggregation functions.
Here, you can learn more about how Pinot handles null values in queries.