Skip to main content
Schema: solana.core Table: fact_events Type: View

​
What

​
Description

This table records every event emitted by on-chain Solana programs during transaction execution. Each row represents a single event, including its type, the program that emitted it, and its position within the transaction. The table covers all events observed on Solana mainnet, including protocol-level and application-level activity. Events are uniquely identified by block, transaction, and event index. This model enables detailed analysis of program behavior, user actions, and protocol interactions at the event level, and is central to understanding the full scope of on-chain activity.

​
Key Use Cases

  • Analyze program interactions and instruction execution flow
  • Track specific program events, methods, or user actions
  • Protocol usage analytics and event-level activity monitoring
  • Avoid complex JSON array parsing from core.fact_transactions by using pre-parsed event fields
  • Downstream analytics for protocol-specific event flows and decoded instructions

​
Important Relationships

  • Closely related to core.fact_events_inner (for inner/CPI events), core.ez_events_decoded (preferred for decoded instruction details), and core.ez_transfers (for transfer events)
  • Use core.fact_events_inner to analyze Cross-Program Invocations (CPIs) and nested program calls
  • Use core.ez_events_decoded for detailed instruction and argument analysis (if program is being decoded)
  • Use core.ez_transfers for asset movement and transfer analytics
  • Joins with core.fact_blocks for block context and core.fact_transactions for transaction context

​
Commonly-used Fields

  • block_timestamp: For time-series and event sequencing analysis
  • block_id, tx_id, index: For unique event identification and joins
  • program_id, event_type: For filtering by program or event type
  • instruction, inner_instruction: For instruction-level analytics
  • signers, succeeded: For user attribution and transaction outcome analysis

​
Sample Queries

​
Event distribution by program with inner instruction metrics

SELECT 
    DATE_TRUNC('day', block_timestamp) AS date,
    program_id,
    COUNT(*) AS event_count,
    COUNT(DISTINCT tx_id) AS unique_transactions,
    AVG(ARRAY_SIZE(inner_instruction_events)) AS avg_inner_events,
    MAX(ARRAY_SIZE(inner_instruction_events)) AS max_inner_events
FROM solana.core.fact_events
WHERE block_timestamp >= CURRENT_DATE - 7
GROUP BY 1, 2
ORDER BY 1 DESC, 3 DESC;

​
Simple event count by program

SELECT 
    program_id,
    COUNT(*) AS total_events
FROM solana.core.fact_events
WHERE block_timestamp >= CURRENT_DATE - 1
GROUP BY program_id
ORDER BY total_events DESC
LIMIT 20;

​
Recent events with basic details

SELECT 
    block_timestamp,
    tx_id,
    program_id,
    instruction_index,
    data
FROM solana.core.fact_events
WHERE block_timestamp >= CURRENT_TIMESTAMP - INTERVAL '1 hour'
ORDER BY block_timestamp DESC
LIMIT 100;

​
Columns

Column NameData TypeDescription
BLOCK_TIMESTAMPTIMESTAMP_NTZThe 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).
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 ‘blockid’ s…
TX_IDTEXTThe 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 bl…
SIGNERSARRAYList 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:…
SUCCEEDEDBOOLEANBoolean 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.
INDEXNUMBERThe position of the transfer event within the list of events for a given Solana transaction. Used to order and reference transfers within a transaction. Indexing starts at 0 for the first event. Data type: Integer Example: 0 (first transfer in the transaction) 2 (third transfer in the transaction) Business Context: Enables reconstruction of transfer order and analysis of intra-transaction asset movement. Used to join, filter, or segment data for protocol analytics, error tracing, and event se…
EVENT_TYPETEXTA 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.
PROGRAM_IDTEXTThe unique public key (base58-encoded address) of a Solana program. This field identifies the on-chain program (smart contract) responsible for processing instructions, emitting events, or managing accounts. Used throughout Solana analytics models—including events, transactions, IDLs, and program activity tables—to join, filter, and analyze program-level data. Example: “4Nd1mY…” “TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA” Business Context: Used as a join key for program activity, deployme…
INSTRUCTIONVARIANTSpecifies which program it is calling, which accounts it wants to read or modify, and additional data that serves as auxiliary input to the program
INNER_INSTRUCTIONVARIANTA call from one smart contract program to another
FACT_EVENTS_IDTEXTA 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_TIMESTAMPTIMESTAMP_NTZThe 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_TIMESTAMPTIMESTAMP_NTZThe 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.