Skip to main content
Schema: solana.nft Table: fact_nft_mint_actions Type: Base Table

​
Description

This table captures detailed minting events for NFTs on Solana, providing granular information about each mint action including the minting authority, amount, and technical details. It tracks the actual minting operations that occur when NFTs are created, burned, or modified, offering insights into the underlying mechanics of NFT lifecycle management and supporting technical analysis of NFT operations.

​
Key Use Cases

  • Track which addresses have authority to mint NFTs and their activity patterns
  • Monitor minting and burning activities that affect NFT supply
  • Study how different programs interact with NFT mints
  • Analyze the technical details of minting operations for debugging and optimization
  • Verify that minting operations follow proper NFT standards

​
Important Relationships

  • Links to nft.dim_nft_metadata via mint address to provide metadata context
  • Connects to nft.fact_nft_mints through mint address for comprehensive mint tracking
  • References core.fact_blocks and core.fact_transactions for blockchain context
  • index and inner_index provide ordering within transaction instructions

​
Commonly-used Fields

  • block_timestamp: Timestamp when the mint action was processed on Solana
  • tx_id: Unique transaction identifier for the mint action
  • mint: The unique mint address of the NFT being acted upon
  • mint_authority: Address of the account with authority to perform the mint action
  • mint_amount: Amount of tokens minted in the action (typically 1 for NFTs)
  • event_type: Type of mint action (e.g., ‘mint’, ‘burn’, ‘transfer’)
  • mint_standard_type: NFT standard being used (e.g., ‘metaplex’, ‘candy_machine’)

​
Columns

Column NameData TypeDescription
BLOCK_IDNUMBERA unique identifier for the block in which this transaction was included on the Solana blockchain. Typically a sequential integer or hash, depending on the data source. Used to group transactions by block and analyze block-level activity.
Example:
  • 123456789
Business Context:
  • Supports block-level analytics, such as block production rate and transaction throughput.
  • Useful for tracing transaction inclusion and block explorer integrations.
Relationships:
  • All transactions with the same ‘block_id’ share the same ‘block_timestamp’. | | BLOCK_TIMESTAMP | TIMESTAMP_NTZ | The timestamp (UTC) at which the block was produced on the Solana blockchain. This field is recorded as a TIMESTAMP data type and represents the precise moment the block was finalized and added to the chain. It is essential for time-series analysis, block production monitoring, and aligning transaction and event data to specific points in time. Used extensively for analytics involving block intervals, network activity trends, and historical lookups. Format: YYYY-MM-DD HH:MI:SS (UTC). | | TX_ID | TEXT | The unique transaction signature (hash) for each transaction on the Solana blockchain. This field is a base58-encoded string, typically 88 characters in length, and serves as the primary identifier for transactions across all Solana data models. Used to join transaction data with related tables (blocks, events, transfers, logs, decoded instructions) and to trace the full lifecycle and effects of a transaction. Essential for transaction-level analytics, debugging, and cross-referencing with block explorers or Solana APIs.
Example:
  • 5Nf6Q2k6v1Qw2k3v4Qw5Nf6Q2k6v1Qw2k3v4Qw5Nf6Q2k6v1Qw2k3v4Qw5Nf6Q2k6v1Qw2k3v4Qw
Business Context:
  • Enables precise tracking, auditing, and attribution of on-chain activity
  • Used for linking transactions to events, logs, and protocol actions
  • Critical for compliance, monitoring, and analytics workflows | | SUCCEEDED | BOOLEAN | Boolean flag indicating whether the transaction was successfully executed and confirmed on the Solana blockchain. A value of TRUE means the transaction was processed without errors; FALSE indicates failure due to program errors, insufficient funds, or other issues.
Example:
  • true
  • false
Business Context:
  • Used to filter for successful transactions in analytics and reporting.
  • Important for error analysis, user experience, and program debugging. | | INDEX | NUMBER | The position of the event (instruction) within the list of instructions for a given Solana transaction. Used to order and reference events within a transaction. Indexing starts at 0 for the first event.
Example:
  • 0
  • 3
Business Context:
  • Enables precise identification and ordering of events within a transaction, which is critical for reconstructing transaction flows and analyzing protocol behavior.
  • Used to join or filter event-level data, especially when multiple events occur in a single transaction. | | INNER_INDEX | NUMBER | The position of the inner instruction or event within the list of inner instructions for a given Solana transaction. Used to order and reference nested (CPI) instructions. Indexing starts at 0 for the first inner instruction.
Example:
  • 0
  • 2
Business Context:
  • Enables precise identification and ordering of nested program calls (Cross-Program Invocations) within a transaction.
  • Critical for analyzing composability, protocol integrations, and the full execution path of complex transactions. | | EVENT_TYPE | TEXT | A string categorizing the type of event or instruction, such as ‘transfer’, ‘mint’, ‘burn’, or protocol-specific actions.
Example:
  • ‘transfer’
  • ‘mint’
  • ‘burn’
Business Context:
  • Enables segmentation and filtering of on-chain activity for analytics and dashboards.
  • Used to group and analyze protocol-specific actions and user behaviors.
Relationships:
  • May be derived from decoded instruction data or protocol-specific logic. | | MINT | TEXT | Unique address representing a specific token | | MINT_AMOUNT | NUMBER | The amount of tokens being minted in the transaction, denominated in the token’s smallest unit (e.g., lamports for SOL, or the base unit for SPL tokens). This field enables token supply analysis and mint tracking.
  • Data type: NUMBER (integer, token’s smallest unit)
  • Business context: Used to track token mints, analyze token supply changes, and measure inflationary pressure.
  • Analytics use cases: Token supply analysis, mint rate tracking, and inflationary token studies.
  • Example: For SOL, 1 SOL = 1,000,000,000 lamports; a value of 1000000000 means 1 SOL minted. | | MINT_AUTHORITY | TEXT | The address of the account that has authority to authorize the mint operation. This field identifies the entity responsible for authorizing the token mint.
  • Data type: STRING (base58 Solana address)
  • Business context: Used to track mint authorities, analyze mint patterns, and identify centralized mint controls.
  • Analytics use cases: Mint authority analysis, centralized vs decentralized mint studies, and token governance tracking.
  • Example: ‘4Nd1mYw4r…’ | | SIGNERS | TEXT | List of accounts that signed the transaction. This field captures all wallet addresses that provided signatures for the transaction, enabling multi-signature analysis and transaction authority tracking.
Data type: ARRAY (list of Solana addresses) Business context: Used to track transaction signers, analyze multi-signature patterns, and identify transaction authorities. Analytics use cases: Multi-signature analysis, transaction authority tracking, and signer pattern studies. Example: [‘9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM’, ‘AnotherAddress…’] | | DECIMAL | NUMBER | Number of decimals in the token value, need to divide amount by 10^decimal | | MINT_STANDARD_TYPE | TEXT | The type of mint following Metaplex mint standards | | FACT_NFT_MINT_ACTIONS_ID | TEXT | A unique, stable identifier for each record in this table. The primary key (PK) ensures that every row is uniquely identifiable and supports efficient joins, lookups, and data integrity across models. The PK may be a natural key (such as a blockchain transaction hash) or a surrogate key generated from one or more fields, depending on the table’s structure and requirements. | | INSERTED_TIMESTAMP | TIMESTAMP_NTZ | The timestamp when this transaction record was first inserted into the analytics database. Used for data freshness tracking and incremental model logic. Format: YYYY-MM-DD HH:MI:SS. Not derived from the blockchain, but from the ETL process. | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | The timestamp when this transaction record was last updated in the analytics database. Used for tracking updates and supporting incremental model logic. Format: YYYY-MM-DD HH:MI:SS. Not derived from the blockchain, but from the ETL process. |