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

ā€‹
Description

This table contains BlockMetadata transactions from the Aptos blockchain, which are special system transactions inserted at the beginning of each block to provide essential block-level information. These transactions include consensus metadata such as proposer information, epoch details, round numbers, and validator voting data. BlockMetadata transactions also serve as epoch boundary markers, triggering reward distribution to validators when an epoch ends. The table provides critical infrastructure data for understanding Aptosā€™s consensus mechanism and block production process.

ā€‹
Key Use Cases

  • Consensus mechanism analysis and validator performance tracking
  • Epoch boundary detection and reward distribution monitoring
  • Block proposer analysis and validator rotation tracking
  • Network governance and consensus participation analysis
  • Block production rate and network efficiency monitoring
  • Validator voting pattern analysis and consensus health assessment

ā€‹
Important Relationships

  • Provides block-level context for transaction analysis in core.fact_transactions
  • Links to block data in core.fact_blocks for comprehensive block analysis
  • Supports consensus analysis and validator performance tracking
  • Enables epoch-based analysis across all core models
  • Provides infrastructure context for network health monitoring

ā€‹
Commonly-used Fields

  • block_number: Primary identifier for linking to block-level analysis
  • proposer: Essential for validator performance and rotation analysis
  • epoch: Critical for epoch-based analysis and reward distribution tracking
  • round: Important for consensus round analysis and block production timing
  • vm_status: Transaction execution status for consensus health monitoring
  • block_timestamp: Primary field for time-series analysis of consensus activity

ā€‹
Columns

Column NameData TypeDescription
BLOCK_NUMBERVARIANTAlso 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. | | VERSION | NUMBER | The version number, also known as the height, represents the sequential position of a transaction in the Aptos blockchain. The first transaction has a version of 0, and each subsequent transaction increments by 1.
Data type: Integer Example:
  • 0 (genesis transaction)
  • 12345678
  • 98765432
Business Context:
  • Unique identifier for ordering transactions chronologically across the entire blockchain.
  • Essential for transaction sequencing and version-based analysis.
  • Enables precise transaction tracking and blockchain state verification. | | TX_HASH | TEXT | Transaction hash is a unique 66-character identifier that is generated when a transaction is executed on the Aptos blockchain.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Primary identifier for linking transaction data across all related tables.
  • Essential for transaction verification and blockchain explorer lookups.
  • Enables correlation of transfers, events, and state changes to specific transactions. | | SUCCESS | BOOLEAN | The boolean value indicating whether the transaction was successfully executed on the Aptos blockchain.
Data type: Boolean Example:
  • true (transaction succeeded)
  • false (transaction failed)
Business Context:
  • Essential for filtering successful transactions and analyzing failure rates.
  • Critical for accurate volume calculations and user experience analysis.
  • Enables debugging and error pattern recognition in transaction analysis. | | TX_TYPE | TEXT | The type of transaction executed on the Aptos blockchain, categorizing transactions by their purpose and origin.
Data type: String Example:
  • user_transaction (regular user-initiated transactions)
  • block_metadata_transaction (system transactions for block metadata)
  • state_checkpoint_transaction (system transactions for state checkpoints)
Business Context:
  • Essential for filtering and categorizing different types of blockchain activity.
  • Critical for separating user activity from system operations in analytics.
  • Enables focused analysis on specific transaction categories and use cases. | | EPOCH | NUMBER | An epoch in the Aptos blockchain represents a duration of time during which blocks are voted on by validators, the validator set is updated, and rewards are distributed. The Aptos mainnet epoch is set to 7200 seconds (two hours).
Data type: Integer Example:
  • 1234
  • 5678
Business Context:
  • Essential for epoch-based analysis and validator performance tracking.
  • Critical for reward distribution analysis and consensus mechanism monitoring.
  • Enables epoch-level analytics and validator set change tracking. | | EVENTS | VARIANT | The events that were emitted during transaction execution, representing notifications and state change announcements.
Data type: String (JSON) Example:
  • [{"type":"0x1::coin::DepositEvent","data":{"amount":"1000000","account":"0x123..."}}]
Business Context:
  • Essential for event-driven analytics and smart contract interaction monitoring.
  • Critical for DeFi protocol analysis and event pattern recognition.
  • Enables comprehensive transaction effect analysis and event correlation. | | CHANGES | VARIANT | The state changes that were executed by the transaction, representing modifications to the blockchainā€™s global state.
Data type: String (JSON) Example:
  • [{"type":"write_resource","address":"0x123...","data":{"coin":{"value":"1000000"}}}]
Business Context:
  • Essential for understanding the impact and effects of transactions on blockchain state.
  • Critical for state transition analysis and transaction effect tracking.
  • Enables comprehensive transaction analysis and state modification monitoring. | | FAILED_PROPOSER_INDICES | VARIANT | Array of indices representing validators that failed to propose blocks in the consensus round.
Data type: Array Example:
  • [1, 3, 5]
  • []
Business Context:
  • Essential for consensus mechanism analysis and validator performance tracking.
  • Critical for understanding block proposal failures and network health.
  • Enables validator performance analytics and consensus reliability reporting. | | ID | TEXT | Unique identifier for the block metadata record, providing a distinct reference for each blockā€™s metadata.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Essential for unique record identification and data integrity.
  • Critical for join operations and metadata record management.
  • Enables precise metadata retrieval and referential integrity maintenance. | | PREVIOUS_BLOCK_VOTES_BITVEC | VARIANT | Bit vector representing the votes from validators on the previous block in the consensus mechanism.
Data type: String Example:
  • 0x1234567890abcdef
Business Context:
  • Essential for consensus mechanism analysis and validator voting tracking.
  • Critical for understanding consensus participation and voting patterns.
  • Enables voting analytics and consensus participation reporting. | | PROPOSER | TEXT | The address of the validator that proposed the block in the Aptos consensus mechanism.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Essential for validator performance analysis and block proposer tracking.
  • Critical for consensus mechanism analysis and validator rotation monitoring.
  • Enables proposer-based analytics and validator participation analysis. | | ROUND | NUMBER | A round number representing a shared counter used to select leaders during an epoch of the Aptos consensus protocol.
Data type: Integer Example:
  • 12345
  • 67890
Business Context:
  • Essential for consensus mechanism analysis and leader selection tracking.
  • Critical for block production analysis and consensus round monitoring.
  • Enables round-based analytics and consensus performance evaluation. | | VM_STATUS | TEXT | The execution status of a transaction as reported by the Aptos Virtual Machine (VM), providing success confirmation or failure details.
Data type: String Example:
  • Executed successfully
  • OUT_OF_GAS
  • INSUFFICIENT_BALANCE
  • INVALID_ARGUMENT
Business Context:
  • Essential for transaction success rate analysis and failure investigation.
  • Critical for debugging transaction issues and understanding failure patterns.
  • Enables user experience analysis and error pattern recognition. | | STATE_CHANGE_HASH | TEXT | The cryptographic hash of the state changes, providing verification of the blockchain state modifications.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Essential for state change verification and integrity validation.
  • Critical for blockchain state consistency and change tracking.
  • Enables state change analytics and integrity reporting. | | ACCUMULATOR_ROOT_HASH | TEXT | The root hash of the Merkle accumulator, providing cryptographic proof of the blockchainā€™s state at a given point.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Essential for blockchain state verification and integrity validation.
  • Critical for consensus mechanism analysis and state synchronization.
  • Enables verification of blockchain state consistency and security. | | EVENT_ROOT_HASH | TEXT | The root hash of the event tree, providing cryptographic proof of all events emitted in the transaction.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Essential for event verification and integrity validation.
  • Critical for event-driven analytics and event correlation analysis.
  • Enables verification of event consistency and security. | | FACT_TRANSACTIONS_BLOCK_METADATA_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. |