Skip to main content
Move is the programming language these three chains run their contracts in, which is what makes them a family. They do not all keep the same records, though, because they store what a transaction changed in two different ways. Aptos and Movement list the changes themselves, and carry blocks, transactions, events, changes, resources, modules and table_items. Sui treats everything on the chain as an object with an owner, and records the objects a transaction touched: blocks, transactions, events, move_calls, move_packages, objects, transaction_objects and wrapped_objects.

Chains

Chainchain_idblockstransactionsevents
Aptosaptosโœ“โœ“โœ“
Movementmovementโœ“โœ“โœ“
Suisuiโœ“โœ“โœ“

Exceptions

  • Suiโ€™s tables differ from the Aptos ones because the chain works differently, not because anything is missing.
  • Suiโ€™s blocks rows are checkpoints rather than blocks, and its transactions and events carry gas costs and execution effects instead of Move-style changes.
  • Aptos and Movement additionally carry changes, resources, modules and table_items, the tables that record what a transaction wrote.
  • Sui additionally carries move_calls, move_packages, objects, transaction_objects and wrapped_objects, the tables that record the objects a transaction touched.

Chain pages

Aptos and Sui have pages of their own. Movement uses the Aptos tables exactly.