sui holds the standardized Sui tables, following the Sui schema documented in the family overview. Sui treats everything on the chain as an object with an owner, which sets it apart from the other Move chains. Its blocks rows are checkpoints, the groups it batches transactions into, rather than blocks in the usual sense. The objects, transaction_objects and wrapped_objects tables record every version of every object a transaction touched.
Above the raw tables sits the rest of the catalog, and Sui shows up in two parts of it: the list of tokens we know about with their daily prices, and the tokenized assets issued on the chain. Tokens covers the token list and the daily price table. Real-world assets and Stablecoins cover the tokenized assets and their daily tables.
Tables
| Table | Since | Description |
|---|---|---|
blocks | 2023-05 | One row per checkpoint. |
transactions | 2023-05 | One row per transaction, with its gas costs and effects attached. |
events | 2023-05 | One row per event a transaction emitted. |
move_calls | 2023-05 | One row per Move call command a transaction executed. |
move_packages | 2023-05 | One row per package version published on chain. |
objects | 2023-04 | One row per object version a transaction wrote, with the object contents. |
transaction_objects | 2023-05 | One row per object a transaction touched, without the contents. |
wrapped_objects | 2023-05 | One row per object wrapped inside another object. |
transaction_expirations | 2026-01 | One row per transaction that expires by a validity window rather than by epoch. |
funds_withdrawals | 2026-05 | One row per address-balance withdrawal a transaction reserved. |
accumulator_writes | 2026-05 | One row per accumulator a transaction merged into or split from. |
objects starts a few weeks earlier than the rest, on 2023-04-12. Use transaction_objects when the question is which objects a transaction touched, and objects when what was in them matters.
- blocks
- transactions
- events
- move_calls
- move_packages
- objects
- transaction_objects
- wrapped_objects
- transaction_expirations
- funds_withdrawals
- accumulator_writes
Sui groups its transactions into checkpoints rather than blocks, and a checkpoint is what this table holds.
blocks contains one row per checkpoint.| Column | Type | Description |
|---|---|---|
timestamp | TIMESTAMP | The time of the checkpoint. Partition column. |
number | INT64 | The checkpoint sequence number. |
digest | STRING | The digest of the checkpoint. |
previous_digest | STRING | The digest of the previous checkpoint. |
epoch | STRING | The epoch of the checkpoint. |
network_total_transactions | INT64 | The cumulative network transaction count at the checkpoint. |
timestamp_ms | INT64 | The checkpoint timestamp, in Unix milliseconds. |
sequence_number | INT64 | The checkpoint sequence number. |
validator_signature | STRING | The combined signature of the validators that approved the checkpoint. |
transaction_count | INT64 | The number of transactions in the checkpoint. |
- Daily checkpoints and transactions
Count checkpoints and the transactions in them per day.
Sample queries
- Transactions by kind
- Priced tokens, daily
- Tokenized assets by market cap
Count transactions and gas costs by transaction kind on one day.