Skip to main content
Schema: aptos.core Table: fact_blocks Type: View

​
Description

This table contains block-level data for the Aptos blockchain, mapping the fundamental block structure that groups transactions for execution. The Aptos blockchain uses blocks for batching and executing transactions, where each block contains a range of transaction versions. A transaction at height 0 is the first transaction (genesis transaction), and a transaction at height 100 is the 101st transaction in the transaction store. This table provides the essential metadata for each block including timestamps, hash values, and transaction counts.

​
Key Use Cases

  • Block-level trend analysis and transaction volume monitoring over time
  • Network performance analysis and block production rate calculations
  • Transaction throughput analysis and network capacity planning
  • Block time analysis and network efficiency metrics
  • Historical block data for network health monitoring and anomaly detection

​
Important Relationships

  • Serves as the foundation for transaction-level analysis in core.fact_transactions
  • Provides block context for transfer events in core.fact_transfers and core.ez_transfers
  • Links to block metadata in core.fact_transactions_block_metadata for enhanced block analysis
  • Supports event analysis in core.fact_events by providing block-level context

​
Commonly-used Fields

  • block_number: Primary identifier for ordering and filtering blocks chronologically
  • block_timestamp: Essential for time-series analysis and temporal filtering of blockchain activity
  • tx_count: Critical for measuring transaction throughput and network activity levels
  • block_hash: Important for block verification and linking to external block explorers
  • first_version and last_version: Key for understanding the transaction range contained within each block

​
Columns

Column NameData TypeDescription
BLOCK_NUMBERNUMBERAlso known as block height. The block number indicates the position of a block in the blockchain, increasing sequentially after the addition of each new block.
Data type: Integer Example:
  • 12345678
  • 98765432
Business Context:
  • Primary identifier for ordering and filtering blockchain data chronologically.
  • Essential for block-level analysis and network growth tracking.
  • Enables correlation of transactions, transfers, and events to specific blocks. | | BLOCK_TIMESTAMP | TIMESTAMP_NTZ | The date and time at which the block was produced on the Aptos blockchain.
Data type: Timestamp Example:
  • 2024-01-15 14:30:25.123456
Business Context:
  • Primary field for time-series analysis and temporal filtering of blockchain activity.
  • Essential for trend analysis, volume calculations, and historical comparisons.
  • Enables time-based grouping and aggregation for analytics and reporting. | | BLOCK_HASH | TEXT | The cryptographic hash of the block header, providing a unique identifier for the block on the Aptos blockchain.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Essential for block verification and linking to external block explorers.
  • Critical for blockchain integrity verification and block identification.
  • Enables cross-reference with external blockchain data sources. | | FIRST_VERSION | NUMBER | The version number of the first transaction included in the block, representing the starting transaction version for that block.
Data type: Integer Example:
  • 12345678
  • 98765432
Business Context:
  • Essential for understanding the transaction range contained within each block.
  • Critical for block-level analysis and transaction sequencing verification.
  • Enables correlation between blocks and their contained transactions. | | LAST_VERSION | NUMBER | The version number of the last transaction included in the block, representing the ending transaction version for that block.
Data type: Integer Example:
  • 12345688
  • 98765442
Business Context:
  • Essential for understanding the transaction range contained within each block.
  • Critical for block-level analysis and transaction sequencing verification.
  • Enables correlation between blocks and their contained transactions. | | TX_COUNT | NUMBER | The total count of transactions included in this block, representing the number of transactions processed in that block.
Data type: Integer Example:
  • 10
  • 50
  • 100
Business Context:
  • Essential for measuring transaction throughput and network capacity analysis.
  • Critical for block-level performance monitoring and network efficiency metrics.
  • Enables trend analysis of transaction volume over time. | | FACT_BLOCKS_ID | TEXT | The unique primary key identifier for each row in the table, ensuring data integrity and uniqueness.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Essential for data integrity and unique row identification.
  • Critical for join operations and data relationship management.
  • Enables precise data retrieval and referential integrity maintenance. | | INSERTED_TIMESTAMP | TIMESTAMP_NTZ | The UTC timestamp when the row was inserted into the table, representing when the data was first recorded.
Data type: Timestamp Example:
  • 2024-01-15 14:30:25.123456
Business Context:
  • Essential for data lineage tracking and insertion timing analysis.
  • Critical for understanding data freshness and processing delays.
  • Enables data quality analysis and processing performance monitoring. | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | The UTC timestamp when the row was last modified, representing when the data was most recently updated.
Data type: Timestamp Example:
  • 2024-01-15 14:30:25.123456
Business Context:
  • Essential for data freshness analysis and update tracking.
  • Critical for understanding data modification patterns and change frequency.
  • Enables data quality monitoring and update performance analysis. |