> 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 |
| ----------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------- |
| 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\_HASH | `TEXT` | The hash of a specific block in the blockchain. |
| BLOCK\_HEIGHT | `FIXED` | Indicates the numerical position of a block within the blockchain. |
| TRANSACTION\_INDEX | `FIXED` | The position or order of a transaction within a block of the blockchain. |
| TRANSACTION\_ID | `TEXT` | Unique identifier assigned to each transaction within the blockchain. |
| SOURCE\_TRANSACTION\_FEE | `FIXED` | The transaction fee amount in lamports. |
| TRANSACTION\_FEE | `FIXED` | The transaction fee amount (in SOL). |
| USD\_TRANSACTION\_FEE | `REAL` | The transaction fee amount priced in USD. |
| COMPUTE\_UNITS\_CONSUMED | `FIXED` | The computational units consumed by the transaction's execution on the Solana network. |
| ERROR | `VARIANT` | The response for error when any failure occurs. |
| RECENT\_BLOCK\_HASH | `TEXT` | A base-58 encoded hash of a recent block used to prevent transaction duplication and to give transactions lifetimes. |
| SIGNATURES | `VARIANT` | List of signatures for the given transaction. |
| SIGNER | `TEXT` | The first signature within the transaction |
| SIGNERS | `ARRAY` | n/a |
| ACCOUNT\_KEYS | `VARIANT` | n/a |
| ADDRESS\_TABLE\_LOOKUPS | `VARIANT` | n/a |
| LOG\_MESSAGES | `VARIANT` | n/a |
| VERSION | `TEXT` | Version number associated with a block or transaction. |
| RETURN\_DATA | `VARIANT` | The most-recent return data generated by an instruction in the transaction. |
| STATUS | `VARIANT` | Indicates the status of the transaction. |
| 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 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 BLOCK\_SLOT, TIMESTAMP, DATETIME, BLOCK\_HASH, BLOCK\_HEIGHT, TRANSACTION\_INDEX, and TRANSACTION\_ID.
* Analyze fee details using SOURCE\_TRANSACTION\_FEE, TRANSACTION\_FEE, and USD\_TRANSACTION\_FEE.
* Evaluate network performance with COMPUTE\_UNITS\_CONSUMED.
* Diagnose potential issues with ERROR and LOG\_MESSAGES.
* Verify transaction authenticity and lineage with SIGNATURES, SIGNER, and SIGNERS.
* Explore additional account details via ACCOUNT\_KEYS and ADDRESS\_TABLE\_LOOKUPS.
* Review protocol version and output using VERSION and RETURN\_DATA.
* Assess transaction outcomes with STATUS.
* Monitor data recency with DATE\_CREATED and DATE\_UPDATED.
💡 For example, you might query TRANSACTION\_ID, USD\_TRANSACTION\_FEE, and STATUS to understand the cost and outcome of a transaction. Additionally, you can analyze SOURCE\_TRANSACTION\_FEE[^1] to gauge typical transaction fees and use BLOCK\_HEIGHT and TRANSACTION\_INDEX to pinpoint exactly where a transaction occurred in the chain, along with other key parameters.
[^1]:
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://glint-analytics.gitbook.io/glint-analytics/querying-and-data-analysis/schema-reference/transactions-table.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.