> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dune.com/llms.txt
> Use this file to discover all available pages before exploring further.

# aptos.move_table_items

> Aptos Move table operations — key-value store changes during transaction execution.

export const TableSample = ({tableName, tableSchema}) => <>
    <div className="hidden dark:block">
      <iframe src={`https://dune.com/embeds/3419983/5785629?table_schema_t6f0df=${tableSchema}&table_name_t6f0df=${tableName}&darkMode=true`} style={{
  width: '100%',
  height: '500px',
  border: 'none',
  marginTop: '10px'
}} />
    </div>
    <div className="dark:hidden">
      <iframe src={`https://dune.com/embeds/3419983/5785629?table_schema_t6f0df=${tableSchema}&table_name_t6f0df=${tableName}`} style={{
  width: '100%',
  height: '500px',
  border: 'none',
  marginTop: '10px'
}} />
    </div>
  </>;

## Table description

The `aptos.move_table_items` table tracks the items stored in Move's table data structures on the Aptos blockchain. The Move table is a high-performance, typed data structure used for storing and querying on-chain data. This table details the key-value pairs stored, facilitating efficient data access and manipulation within smart contracts.

## Table Schema

| Column                              | Type              | Description                                                             |
| ----------------------------------- | ----------------- | ----------------------------------------------------------------------- |
| `block_height`                      | `BIGINT`          | Sequential number identifying the block's position in the chain         |
| `block_date`                        | `DATE`            | Date of the block for daily aggregations                                |
| `block_time`                        | `TIMESTAMP`       | Timestamp when the block was committed                                  |
| `block_hash`                        | `VARBINARY`       | Unique cryptographic hash identifying the block                         |
| `block_first_version`               | `UINT256`         | First transaction version included in the block                         |
| `block_last_version`                | `UINT256`         | Last transaction version included in the block                          |
| `block_proposer`                    | `VARBINARY`       | Address of the validator that proposed the block                        |
| `block_round`                       | `UINT256`         | Consensus round number for the block                                    |
| `block_epoch`                       | `UINT256`         | Epoch number during which the block was created                         |
| `block_metadata_id`                 | `VARBINARY`       | Unique identifier for the block metadata event                          |
| `block_failed_proposer_indices`     | `ARRAY(INTEGER)`  | Indices of validators that failed to propose before this block          |
| `block_previous_block_votes_bitvec` | `ARRAY(SMALLINT)` | Bit vector of validator votes on the previous block                     |
| `tx_index`                          | `INTEGER`         | Position of the transaction within the block                            |
| `tx_type`                           | `VARCHAR`         | Type of the transaction (e.g. user\_transaction, block\_metadata)       |
| `tx_hash`                           | `VARBINARY`       | Unique hash identifying the transaction                                 |
| `tx_version`                        | `UINT256`         | Global sequential version number of the transaction                     |
| `tx_gas_used`                       | `UINT256`         | Amount of gas consumed by the transaction                               |
| `tx_vm_status`                      | `VARCHAR`         | Detailed status message returned by the Move VM                         |
| `tx_success`                        | `BOOLEAN`         | Whether the transaction executed successfully                           |
| `tx_state_change_hash`              | `VARBINARY`       | Hash of all state changes produced by the transaction                   |
| `tx_event_root_hash`                | `VARBINARY`       | Merkle root hash of all events emitted by the transaction               |
| `tx_state_checkpoint_hash`          | `VARBINARY`       | Hash of the state checkpoint after this transaction                     |
| `tx_accumulator_root_hash`          | `VARBINARY`       | Root hash of the transaction accumulator after this transaction         |
| `write_set_change_index`            | `INTEGER`         | Index of this state change within the transaction's write set           |
| `write_set_change_type`             | `VARCHAR`         | Type of write set change (e.g. write\_table\_item, delete\_table\_item) |
| `move_state_key_hash`               | `VARBINARY`       | Hash of the state key affected by this change                           |
| `move_is_deletion`                  | `BOOLEAN`         | Whether this change represents a deletion of the table item             |
| `move_table_item_handle`            | `VARBINARY`       | Handle identifying the on-chain Move table this item belongs to         |
| `move_table_item_key`               | `VARBINARY`       | Serialized key of the item within the Move table                        |
| `move_table_item_value`             | `VARBINARY`       | Serialized value of the item within the Move table                      |
| `move_data`                         | `VARCHAR`         | JSON-encoded representation of the table item data                      |

## Table Sample

<TableSample tableSchema="aptos" tableName="move_table_items" />