Skip to main content
Schema: solana.gov Table: dim_epoch Type: View

​
Description

This table contains epoch information for the Solana blockchain, including the block range for each epoch. It serves as a dimension table that provides epoch context for governance and staking analytics, enabling time-based analysis across different epochs and supporting epoch-level aggregations.

​
Key Use Cases

  • Provide epoch context for governance and staking analytics
  • Enable epoch-based filtering and grouping of blockchain data
  • Support time-series analysis across different epochs
  • Facilitate epoch-level aggregations and reporting
  • Track epoch progression and block range changes

​
Important Relationships

  • Links to gov.fact_validators via epoch for validator performance analysis
  • Connects to gov.fact_proposal_votes through epoch context for governance timeline analysis
  • References gov.fact_rewards_staking and gov.fact_rewards_voting for epoch-based reward tracking
  • Provides epoch context for gov.fact_stake_accounts and gov.fact_vote_accounts

​
Commonly-used Fields

  • epoch: The epoch number identifier
  • start_block: The first block number in the epoch
  • end_block: The last block number in the epoch

​
Columns

Column NameData TypeDescription
EPOCHNUMBERA period of time consisting of 432,000 blocks, which represents a higher-level timekeeping unit within the Solana network
START_BLOCKNUMBERThe first block within an Epoch
END_BLOCKNUMBERThe last block within an Epoch
DIM_EPOCH_IDTEXTA unique identifier for the record.
MODIFIED_TIMESTAMPTIMESTAMP_NTZThe timestamp when this transaction record was last updated in the analytics database. Used for tracking updates and supporting incremental model logic. Format: YYYY-MM-DD HH:MI:SS. Not derived from the blockchain, but from the ETL process.
INSERTED_TIMESTAMPTIMESTAMP_NTZThe timestamp when this transaction record was first inserted into the analytics database. Used for data freshness tracking and incremental model logic. Format: YYYY-MM-DD HH:MI:SS. Not derived from the blockchain, but from the ETL process.