mirror of
https://github.com/FlipsideCrypto/solana-models.git
synced 2026-02-06 11:47:08 +00:00
* description rules and fact_txs update * blocks update * idls and labels * wip * wip * update desc * update * update doc rules * update table desc per new rules * updates
2.0 KiB
2.0 KiB
{% docs fact_events %}
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_transactionsby 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), andcore.fact_transfers(for transfer events) - Use
core.fact_events_innerto analyze Cross-Program Invocations (CPIs) and nested program calls - Use
core.ez_events_decodedfor detailed instruction and argument analysis (if program is being decoded) - Use
core.fact_transfersfor asset movement and transfer analytics - Joins with
core.fact_blocksfor block context andcore.fact_transactionsfor transaction context
Commonly-used Fields
block_timestamp: For time-series and event sequencing analysisblock_id,tx_id,index: For unique event identification and joinsprogram_id,event_type: For filtering by program or event typeinstruction,inner_instruction: For instruction-level analyticssigners,succeeded: For user attribution and transaction outcome analysis
{% enddocs %}