sui.core Table: fact_checkpoints Type: Base Table
Fact table representing all finalized checkpoints on the Sui blockchain, which serve as consensus
points bundling multiple transactions for finality and recovery. Each checkpoint aggregates metadata
such as checkpoint sequence number, timestamp, transaction count, validator signatures, and epoch
information. Checkpoints are produced via the Mysticeti consensus mechanism approximately every
250ms, providing the backbone for time series analysis (TPS, latency, validator participation). This
table is essential for measuring network throughput, tracking validator performance, and ensuring
data integrity. Supports analytics on epoch transitions, validator set changes, and network health.
Data Coverage: This table contains full historical coverage from April 2023 - Present
(201.1M rows), covering all checkpoints since the launch of Sui mainnet.
Columns
| Column Name | Data Type | Description |
|---|---|---|
| CHECKPOINT_NUMBER | NUMBER | The sequential number of the checkpoint in which this record was finalized on the Sui blockchain. Checkpoints are consensus milestones that bundle and finalize multiple transactions, providing the primary unit of finality and recovery in Sui. Starts at 0 (genesis checkpoint) and increments by one for each new checkpoint. Used for time series analysis, transaction ordering, and measuring network throughput. Once a transaction is included in a checkpoint, it is permanently recorded and cannot be reverted. This dataset only includes checkpoints greater than or equal to 96605300. Example: 96605301. |
| BLOCK_TIMESTAMP | TIMESTAMP_NTZ | The network-agreed timestamp (in milliseconds since Unix epoch) when the checkpoint containing this record was finalized by Sui consensus. Represents the authoritative time of transaction finality, as determined by validator signatures. Used for temporal analytics, trend analysis, and aligning on-chain activity with real-world time. Example: ‘2024-06-01 12:34:56.789’. |
| EPOCH | NUMBER | Epoch number (integer) representing a fixed period (~24h) with a stable validator set and protocol configuration. Used for tracking validator changes, protocol upgrades, and time-based partitioning. Example: 42. |
| CHECKPOINT_DIGEST | TEXT | 32-byte cryptographic hash (Base58) uniquely identifying checkpoint contents. Used for checkpoint verification, integrity checking, and chain continuity. Example: ‘6Qk8…9Xz’. |
| PREVIOUS_DIGEST | TEXT | Hash of the previous checkpoint, maintaining blockchain continuity. Used for history verification and chain analysis. Example: ‘5Jk7…8Yz’. |
| NETWORK_TOTAL_TRANSACTIONS | NUMBER | Cumulative count of all transactions processed by the network up to this checkpoint. Monotonically increasing integer, key metric for network growth, adoption, and throughput analysis. Example: 10000000. |
| VALIDATOR_SIGNATURE | TEXT | Aggregated BLS signature (Base64) from validator quorum (>2/3) for checkpoint finality. Provides Byzantine fault-tolerant consensus proof. Used for security analysis and validator participation tracking. Example: ‘MEUCIQ…’. |
| TX_COUNT | NUMBER | Total number of transactions included in the checkpoint. Used for measuring checkpoint size, throughput, and network performance. Example: 250. |
| TRANSACTIONS_ARRAY | VARIANT | Array of transaction digests included in the checkpoint. Used for transaction finality tracking, checkpoint analysis, and reconstructing checkpoint composition. Example: [‘6Qk8…9Xz’, ‘7Yl2…3Ab’]. |
| FACT_CHECKPOINTS_ID | TEXT | Surrogate key for the checkpoint fact table. Generated unique identifier for each checkpoint record, typically constructed from the checkpoint number or digest. Ensures row-level uniqueness and supports efficient joins, indexing, and lineage tracing across all checkpoint-related analytics. In Sui, this enables fast correlation of checkpoint metadata with transactions, validator signatures, and epoch transitions. Essential for time series analysis, network health monitoring, and data integrity verification. |
| INSERTED_TIMESTAMP | TIMESTAMP_NTZ | Timestamp when the record was inserted into the analytics database. System-generated by the ETL pipeline, typically in TIMESTAMP_NTZ format. Used for data lineage, ETL monitoring, and freshness checks. In Sui analytics, this field is essential for tracking data ingestion latency, validating pipeline health, and supporting incremental model builds. Example: ‘2024-06-01 12:34:56.789’. |
| MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | Timestamp when the record was last modified in the analytics database. System-generated for change tracking, data versioning, and consistency verification. In Sui, this supports incremental processing, late-arriving data correction, and auditability of analytics workflows. Used to monitor data staleness and trigger downstream updates. Example: ‘2024-06-01 12:34:56.789’. |