> 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/transactions-table.md).

# Transactions Table

Transactions are made up of only successful transactions and contain details, including the amount of native tokens and gas that was used in the transaction.

| Name                                | Type            | Description                                                                                                          |
| ----------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------- |
| <kbd>BLOCK\_SLOT</kbd>              | `FIXED`         | Slot number or identifier of the block.                                                                              |
| <kbd>TIMESTAMP</kbd>                | `FIXED`         | Raw value of the time in Unix Epoch time (in UTC time zone), which is then converted to DATETIME column.             |
| <kbd>DATETIME</kbd>                 | `TIMESTAMP_NTZ` | Timestamp of the transaction in UTC.                                                                                 |
| <kbd>BLOCK\_HASH</kbd>              | `TEXT`          | The hash of a specific block in the blockchain.                                                                      |
| <kbd>BLOCK\_HEIGHT</kbd>            | `FIXED`         | Indicates the numerical position of a block within the blockchain.                                                   |
| <kbd>TRANSACTION\_INDEX</kbd>       | `FIXED`         | The position or order of a transaction within a block of the blockchain.                                             |
| <kbd>TRANSACTION\_ID</kbd>          | `TEXT`          | Unique identifier assigned to each transaction within the blockchain.                                                |
| <kbd>SOURCE\_TRANSACTION\_FEE</kbd> | `FIXED`         | The transaction fee amount in lamports.                                                                              |
| <kbd>TRANSACTION\_FEE</kbd>         | `FIXED`         | The transaction fee amount (in SOL).                                                                                 |
| <kbd>USD\_TRANSACTION\_FEE</kbd>    | `REAL`          | The transaction fee amount priced in USD.                                                                            |
| <kbd>COMPUTE\_UNITS\_CONSUMED</kbd> | `FIXED`         | The computational units consumed by the transaction's execution on the Solana network.                               |
| <kbd>ERROR</kbd>                    | `VARIANT`       | The response for error when any failure occurs.                                                                      |
| <kbd>RECENT\_BLOCK\_HASH</kbd>      | `TEXT`          | A base-58 encoded hash of a recent block used to prevent transaction duplication and to give transactions lifetimes. |
| <kbd>SIGNATURES</kbd>               | `VARIANT`       | List of signatures for the given transaction.                                                                        |
| <kbd>SIGNER</kbd>                   | `TEXT`          | The first signature within the transaction                                                                           |
| <kbd>SIGNERS</kbd>                  | `ARRAY`         | n/a                                                                                                                  |
| <kbd>ACCOUNT\_KEYS</kbd>            | `VARIANT`       | n/a                                                                                                                  |
| <kbd>ADDRESS\_TABLE\_LOOKUPS</kbd>  | `VARIANT`       | n/a                                                                                                                  |
| <kbd>LOG\_MESSAGES</kbd>            | `VARIANT`       | n/a                                                                                                                  |
| <kbd>VERSION</kbd>                  | `TEXT`          | Version number associated with a block or transaction.                                                               |
| <kbd>RETURN\_DATA</kbd>             | `VARIANT`       | The most-recent return data generated by an instruction in the transaction.                                          |
| <kbd>STATUS</kbd>                   | `VARIANT`       | Indicates the status of the transaction.                                                                             |
| <kbd>DATE\_CREATED</kbd>            | `TIMESTAMP_NTZ` | Indicates the date in which the data was loaded.                                                                     |
| <kbd>DATE\_UPDATED</kbd>            | `TIMESTAMP_NTZ` | Indicates the date in which the data was updated.                                                                    |

🔍 Use these columns to gather comprehensive insights into successful transactions on the Solana blockchain, including detailed information on transaction context, fee structures, network performance, and data recency, among others. You can:

* Identify the block and transaction context using <kbd>BLOCK\_SLOT</kbd>, <kbd>TIMESTAMP</kbd>, <kbd>DATETIME</kbd>, <kbd>BLOCK\_HASH</kbd>, <kbd>BLOCK\_HEIGHT</kbd>, <kbd>TRANSACTION\_INDEX</kbd>, and <kbd>TRANSACTION\_ID</kbd>.
* Analyze fee details using <kbd>SOURCE\_TRANSACTION\_FEE</kbd>, <kbd>TRANSACTION\_FEE</kbd>, and <kbd>USD\_TRANSACTION\_FEE</kbd>.
* Evaluate network performance with <kbd>COMPUTE\_UNITS\_CONSUMED</kbd>.
* Diagnose potential issues with <kbd>ERROR</kbd> and <kbd>LOG\_MESSAGES</kbd>.
* Verify transaction authenticity and lineage with <kbd>SIGNATURES</kbd>, <kbd>SIGNER</kbd>, and <kbd>SIGNERS</kbd>.
* Explore additional account details via <kbd>ACCOUNT\_KEYS</kbd> and <kbd>ADDRESS\_TABLE\_LOOKUPS</kbd>.
* Review protocol version and output using <kbd>VERSION</kbd> and <kbd>RETURN\_DATA</kbd>.
* Assess transaction outcomes with <kbd>STATUS</kbd>.
* Monitor data recency with <kbd>DATE\_CREATED</kbd> and <kbd>DATE\_UPDATED</kbd>.

💡 For example, you might query <kbd>TRANSACTION\_ID,</kbd> <kbd>USD\_TRANSACTION\_FEE</kbd>, and <kbd>STATUS</kbd> to understand the cost and outcome of a transaction. Additionally, you can analyze SOURCE\_TRANSACTION\_FEE[^1] to gauge typical transaction fees and use <kbd>BLOCK\_HEIGHT</kbd> and TRANSACTION\_INDEX to pinpoint exactly where a transaction occurred in the chain, along with other key parameters.

[^1]: