Sui

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. It has no blocks in the usual sense either: its blocks rows are checkpoints, the groups it batches transactions into. The objects, transaction_objects and wrapped_objects tables record every version of every object a transaction touched.

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.

Columns

Sui treats everything as an object with an owner, and records the objects a transaction touched.

Every table except blocks splits by day on block_timestamp, and blocks on timestamp. Bound that column in every query; without a bound the query reads the whole table.

blocks
transactions
events

Sui has no blocks in the usual sense. It groups its transactions into checkpoints instead, 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`	STRING	The checkpoint timestamp, in milliseconds.
`sequence_number`	STRING	The checkpoint sequence number as a string.
`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 they carry per day.

select
    date(timestamp) as day,
    count(*) as checkpoints,
    sum(transaction_count) as transactions
from `sui.blocks`
where timestamp >= timestamp('2026-08-20')
  and timestamp < timestamp('2026-08-21')
group by day

transactions contains one row per transaction, with what it cost to run and its effects, the chain’s own record of everything the transaction changed, attached to the row.

Column	Type	Description
`block_timestamp`	TIMESTAMP	The time of the containing checkpoint. Partition column.
`block_number`	INT64	The sequence number of the containing checkpoint.
`digest`	STRING	The digest of the transaction, the identifier used everywhere else.
`checkpoint`	STRING	The checkpoint sequence number as a string.
`timestamp_ms`	STRING	The transaction timestamp, in milliseconds.
`sender`	STRING	The sending address.
`transaction_kind`	STRING	The transaction kind, such as programmable transaction.
`is_system_txn`	BOOL	Whether the transaction is a system transaction.
`is_sponsored_tx`	BOOL	Whether the gas was paid by a sponsor.
`status`	STRING	The execution status.
`computation_cost`	BIGNUMERIC	The computation cost, in MIST.
`storage_cost`	BIGNUMERIC	The storage cost, in MIST.
`storage_rebate`	BIGNUMERIC	The storage rebate, in MIST.
`non_refundable_storage_fee`	BIGNUMERIC	The non-refundable part of the storage fee, in MIST.
`total_gas_cost`	BIGNUMERIC	The total gas cost, in MIST.
`gas_budget`	BIGNUMERIC	The gas budget set by the sender.
`gas_price`	BIGNUMERIC	The gas price paid.
`gas_owner`	STRING	The address paying the gas.
`executed_epoch`	STRING	The epoch the transaction executed in.
`transaction_json`	STRING	The full transaction, as JSON text.
`effects_json`	STRING	The full execution effects, as JSON text.
`balance_changes_json`	STRING	The balance changes, as JSON text.

Daily transactions by kind

Count transactions and successes by transaction kind on one day.

select
    transaction_kind,
    count(*) as transactions,
    countif(status = 'success') as successful
from `sui.transactions`
where block_timestamp >= timestamp('2026-08-20')
  and block_timestamp < timestamp('2026-08-21')
group by transaction_kind
order by transactions desc

An event is a note that published code writes when something happens inside it. events contains one row per event a transaction produced.

Column	Type	Description
`block_timestamp`	TIMESTAMP	The time of the containing checkpoint. Partition column.
`block_number`	INT64	The sequence number of the containing checkpoint.
`transaction_digest`	STRING	The digest of the emitting transaction.
`checkpoint`	STRING	The checkpoint sequence number as a string.
`epoch`	STRING	The epoch of the event.
`event_index`	INT64	The position of the event within the transaction.
`package_id`	STRING	The package that defines the event type.
`module`	STRING	The module that defines the event type.
`sender`	STRING	The sender of the emitting transaction.
`event_type`	STRING	The Move type of the event.
`event_json`	STRING	The event payload, as JSON text.

Events by module

Rank the modules emitting the most events on one day.

select
    module,
    count(*) as events
from `sui.events`
where block_timestamp >= timestamp('2026-08-20')
  and block_timestamp < timestamp('2026-08-21')
group by module
order by events desc
limit 20

Sample queries

Transactions by kind
Priced tokens, daily
Tokenized assets by market cap

Count transactions and gas costs by transaction kind on one day.

select
    transaction_kind,
    count(*) as transactions,
    sum(total_gas_cost) as total_gas_cost_mist
from `sui.transactions`
where block_timestamp >= timestamp('2026-08-20')
  and block_timestamp < timestamp('2026-08-21')
group by transaction_kind
order by transactions desc

Count the Sui tokens that carry a daily USD price, day by day.

select
    date(timestamp) as day,
    count(distinct token_id) as priced_tokens
from `metrics_tokens.price_daily`
where timestamp >= timestamp('2026-08-16')
  and timestamp < timestamp('2026-08-23')
  and chain_id = 'sui'
group by day
order by day

Rank the tokenized assets deployed on Sui by circulating market cap.

select
    assets.symbol,
    assets.asset_type,
    daily.market_cap_circulating_total
from `metrics_asset_tokens.market_cap_circulating_total_daily` as daily
join `dimensions.asset_tokens` as deployments
    using (asset_token_id)
join `dimensions.assets` as assets
    using (asset_id)
where daily.timestamp >= timestamp('2026-08-22')
  and daily.timestamp < timestamp('2026-08-23')
  and deployments.chain_id = 'sui'
order by daily.market_cap_circulating_total desc
limit 20

Notes

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. 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 the daily prices they carry, and the tokenized assets issued on the chain. No app or trading-pool table covers Sui. Tokens covers the token list and the daily price table. Tokenized assets and Stablecoins cover the tokenized assets and their daily tables.

Overview

Core entities

Core datasets

Market verticals

Chain verticals

Tables

Columns

Sample queries

Notes

​Tables

​Columns

​Sample queries

​Notes

Tables

Columns

Sample queries

Notes