Skip to main content
Schema: solana.gov Table: fact_votes_agg_block Type: Base Table

​
Description

This table contains aggregated vote data by block, providing a summary view of voting activity and consensus participation across the Solana network. It tracks vote account participation in block validation and consensus, enabling analysis of network consensus patterns and validator voting behavior.

​
Key Use Cases

  • Analyze consensus participation patterns by block
  • Track vote account voting frequency and reliability
  • Monitor network consensus health and participation rates
  • Study validator voting patterns and network consensus
  • Support network health analysis and consensus metrics

​
Important Relationships

  • Links to gov.fact_vote_accounts through vote_pubkey for vote account analysis
  • Connects to gov.fact_validators for validator performance analysis
  • References core.fact_blocks for block context
  • Provides consensus context for network analytics

​
Commonly-used Fields

  • block_id: Block number for the aggregated votes
  • vote_pubkey: Address of the vote account
  • vote_balance: Voting balance of the account
  • vote_credits: Vote credits earned by the account

​
Columns

Column NameData TypeDescription
BLOCK_TIMESTAMPTIMESTAMP_NTZThe timestamp (UTC) at which the block was produced on the Solana blockchain. This field is recorded as a TIMESTAMP data type and represents the precise moment the block was finalized and added to the chain. It is essential for time-series analysis, block production monitoring, and aligning transaction and event data to specific points in time. Used extensively for analytics involving block intervals, network activity trends, and historical lookups. Format: YYYY-MM-DD HH:MI:SS (UTC).
BLOCK_IDNUMBERA unique identifier for the block in which this transaction was included on the Solana blockchain. Typically a sequential integer or hash, depending on the data source. Used to group transactions by block and analyze block-level activity.
Example:
  • 123456789
Business Context:
  • Supports block-level analytics, such as block production rate and transaction throughput.
  • Useful for tracing transaction inclusion and block explorer integrations.
Relationships:
  • All transactions with the same ‘block_id’ share the same ‘block_timestamp’. | | NUM_VOTES | NUMBER | The number of vote events that occurred within the block. This field tracks the count of voting transactions processed in a specific block, enabling consensus participation analysis and block-level voting activity measurement.
Data type: INTEGER (vote count) Business context: Used to analyze consensus participation patterns, track voting activity by block, and measure network consensus health. Analytics use cases: Consensus participation analysis, voting activity tracking, and network consensus health measurement. Example: 5, 10, 20 | | FACT_VOTES_AGG_BLOCK_ID | TEXT | A unique, stable identifier for each record in this table. The primary key (PK) ensures that every row is uniquely identifiable and supports efficient joins, lookups, and data integrity across models. The PK may be a natural key (such as a blockchain transaction hash) or a surrogate key generated from one or more fields, depending on the table’s structure and requirements. | | INSERTED_TIMESTAMP | TIMESTAMP_NTZ | The 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. | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | The 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. |