Glint Analytics
  • Glint Quick Start Guide
  • GETTING STARTED
    • What is Glint?
    • How to Create a Glint Account?
  • Dashboards
    • Creating a New Dashboard
    • Opening Trending Dashboards
  • DASHBOARD EDITING
    • Dashboard Editor Overview
      • Adding Portlets
      • Moving, Resizing and Arranging Portlets
      • Adjusting Portlet Appearance
      • Portlet Types and Settings
        • Chart Portlets
          • Chart Portlet Settings
        • Network Portlets
          • Network Portlet Settings
        • Dynamic Portlets
          • Dynamic Portlet Settings
        • Static Portlets
          • Text Portlet Settings
          • Image Portlet Settings
      • Additional Dashboard Options
        • Opening My Dashboards
        • Adding Dashboard Pages
        • Saving, Publishing, and Deleting Dashboards
  • QUERYING AND DATA ANALYSIS
    • Writing Queries
      • Using the AI Assistant
      • Manually Using SQL
      • Using the Query Builder
    • Schema Reference
      • Blocks Table
      • Instructions Table
      • Instructions Failed Table
      • Priced Net Transfers Table
      • Priced Net Transfers Failed Table
      • Priced Transfers Table
      • Priced Transfers Failed Table
      • Rewards Table
      • Tokens Table
      • Transactions Table
      • Transactions Failed Table
  • REWARDS
    • Reward Process and Mechanism
  • PLATFORM OVERVIEW
    • Supported Chains
Powered by GitBook
On this page
  1. QUERYING AND DATA ANALYSIS
  2. Schema Reference

Transactions Table

PreviousTokens TableNextTransactions Failed Table

Last updated 5 months ago

CtrlK

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 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.