Skip to main content
Schema: bitcoin.gov Table: ez_miner_rewards Type: View

​
What

​
Description

This table contains comprehensive mining reward data for all Bitcoin blocks, providing detailed breakdowns of block rewards, transaction fees, and total miner compensation. Each row represents a single block with its associated mining economics including the fixed block reward (which halves every 210,000 blocks), transaction fees collected, and the total reward received by the miner. This table is essential for understanding Bitcoin’s mining economics, fee market dynamics, and the financial incentives that secure the network.

​
Key Use Cases

  • Mining economics analysis and profitability studies
  • Block reward halving event analysis and impact assessment
  • Transaction fee market analysis and blockspace economics
  • Mining pool revenue tracking and performance comparison
  • Network security analysis through mining incentive monitoring
  • Historical mining reward trends and Bitcoin emission analysis
  • Fee market dynamics and transaction prioritization studies

​
Important Relationships

  • Aggregates mining reward data from core.fact_blocks and core.fact_transactions
  • Provides mining economics context for core.fact_clustered_transfers entity analysis
  • Supports stats.ez_core_metrics_hourly for aggregated mining metrics
  • Enables integration with core.dim_entity_clusters for mining pool analysis
  • Complements price.ez_prices_hourly for mining profitability analysis

​
Commonly-used Fields

  • block_timestamp: Essential for time-series analysis and trend detection
  • block_number: Critical for chronological ordering and halving event analysis
  • total_reward: Key metric for mining profitability and network security analysis
  • block_reward: Important for Bitcoin emission analysis and halving studies
  • fees: Essential for fee market analysis and blockspace economics
  • coinbase_decoded: Critical for mining pool identification and attribution

​
Columns

Column NameData TypeDescription
BLOCK_TIMESTAMPTIMESTAMP_NTZThe timestamp (TIMESTAMP_NTZ, UTC) of the block that contains this transaction. This value is inherited from the block header and represents when the block was mined and the transaction was confirmed on-chain. Example: 2024-06-01 12:34:56.000
BLOCK_NUMBERNUMBERThe block height (INTEGER) of the block containing this transaction. In Bitcoin, block height is the number of blocks preceding a particular block in the blockchain, starting from the genesis block (height 0). Example: 845000
BLOCK_HASHTEXTThe 64-character hexadecimal hash (STRING) of the block containing this transaction. This value uniquely identifies the block in the Bitcoin blockchain. Example: 0000000000000000000a16b7e2e3b2c1d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8g9
COINBASE_DECODEDTEXTThe decoded coinbase message for a block, if applicable.
TOTAL_REWARDFLOATThe output value of the coinbase of the transactions. This is taken directly from the coinbase output, and representes the total fees and reward paid to the miner of this block.
BLOCK_REWARDFLOATThe reward paid to the miner of this block. This is computed as the output of the coinbase transactions, less transaction fees.
FEESFLOATThe transaction fee (FLOAT, BTC) paid by this transaction, calculated as the difference between the sum of input values and the sum of output values. In Bitcoin’s UTXO model, transaction fees are the primary incentive for miners to include transactions in blocks. Higher fees increase the likelihood of faster confirmation as miners prioritize transactions with better fee-to-size ratios. Fees are essential for network security and help prevent spam transactions. The fee market is dynamic and re…
EZ_MINER_REWARDS_IDTEXTA unique identifier (STRING or NUMBER) for the record, used as a primary key for this table. Not a blockchain-native field. Example: 123456789
INSERTED_TIMESTAMPTIMESTAMP_NTZThe timestamp (TIMESTAMP_NTZ, UTC) when this record was initially created and inserted into the table. Example: 2024-06-01 12:34:56.000
MODIFIED_TIMESTAMPTIMESTAMP_NTZThe timestamp (TIMESTAMP_NTZ, UTC) when this record was last modified by an internal process. Example: 2024-06-01 12:35:00.000