> For the complete documentation index, see [llms.txt](https://glint-analytics.gitbook.io/glint-analytics/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glint-analytics.gitbook.io/glint-analytics/querying-and-data-analysis/schema-reference/blocks-table.md).

# Blocks Table

Blocks are where batches of transactions are processed together. This table provides all the details about the block activity.

| Name                               | Type            | Description                                                                                              |
| ---------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------- |
| `BLOCK_SLOT`                       | `FIXED`         | Slot number or identifier of the block.                                                                  |
| `TIMESTAMP`                        | `FIXED`         | Raw value of the time in Unix Epoch time (in UTC time zone), which is then converted to DATETIME column. |
| `DATETIME`                         | `TIMESTAMP_NTZ` | Timestamp of the transaction in UTC.                                                                     |
| `BLOCK_HEIGHT`                     | `FIXED`         | The hash of a specific block in the chain.                                                               |
| `BLOCK_HASH`                       | `TEXT`          | The hash of a specific block in the blockchain.                                                          |
| `PARENT_SLOT`                      | `FIXED`         | Slot number of the parent block.                                                                         |
| `PREVIOUS_BLOCK_HASH`              | `TEXT`          | Block hash of the previous block in the blockchain.                                                      |
| `TOTAL_TRANSACTIONS`               | `FIXED`         | n/a                                                                                                      |
| `TOTAL_NON_VOTE_TRANSACTIONS`      | `FIXED`         | n/a                                                                                                      |
| `SUCCESSFUL_NON_VOTE_TRANSACTIONS` | `FIXED`         | n/a                                                                                                      |
| `IS_REORG`                         | `BOOLEAN`       | Indicates whether the block was involved in a reorg.                                                     |
| `DATE_CREATED`                     | `TIMESTAMP_NTZ` | Indicates the date in which the data was loaded.                                                         |
| `DATE_UPDATED`                     | `TIMESTAMP_NTZ` | Indicates the date in which the data was updated.                                                        |

🔍 Use these columns to gather comprehensive insights into block-level data, such as the number of transactions processed or the block’s position in the chain. You can:

* Identify each block via `BLOCK_SLOT` and `BLOCK_HASH`.
* Track when blocks were produced using `TIMESTAMP` and `DATETIME`.
* Determine block positions with `BLOCK_HEIGHT`.
* Analyze parent/previous relationships using `PARENT_SLOT` and `PREVIOUS_BLOCK_HASH`.
* Monitor transaction volume per block via `TOTAL_TRANSACTIONS`, `TOTAL_NON_VOTE_TRANSACTIONS`, and `SUCCESSFUL_NON_VOTE_TRANSACTIONS`.
* Detect reorganization events with `IS_REORG`.
* Assess data recency with `DATE_CREATED` and `DATE_UPDATED.`

For example, you might query `DATETIME`, `BLOCK_HASH`, and `IS_REORG` to capture exact block production timings and uncover any reorganization events.