flow.core_evm Table: fact_event_logs Type: Base Table
Description
A comprehensive fact table containing event log data emitted by smart contracts on EVM-compatible blockchains. This table serves as the foundation for smart contract analysis, providing detailed information about events including contract addresses, topics, data, and execution context. The table supports analysis of DeFi protocols, NFT marketplaces, and other smart contract applications across multiple EVM chains. Each record represents a single event log with complete emission details and metadata.Key Use Cases
- Smart Contract Analysis: Understanding contract behavior and event emission patterns
- DeFi Protocol Analysis: Tracking DeFi events, swaps, liquidity changes, and yield farming activities
- NFT Analytics: Monitoring NFT transfers, sales, and marketplace activities
- Event Tracking: Following specific event types across different contracts and chains
- Contract Interaction Analysis: Understanding how users interact with smart contracts
- Cross-Chain Event Analysis: Comparing event patterns across different EVM-compatible blockchains
Important Relationships
- core_evm__fact_transactions: Links to transactions that emitted these events
- core_evm__fact_blocks: Links to blocks containing event logs
- core_evm__dim_contracts: Links to contract metadata for event source identification
- core_evm__dim_labels: Links to address labels for contract and user identification
- core_evm__ez_token_transfers: May link to curated token transfer events
- core__fact_events: May provide comparison data with native Flow events
Commonly-used Fields
- CONTRACT_ADDRESS: Essential for contract identification and event source analysis
- TOPIC_0: Critical for event type identification and event categorization
- TOPICS: Important for event parameter analysis and filtering
- DATA: Key for event data extraction and parameter analysis
- TX_HASH: Essential for linking events to their originating transactions
- BLOCK_TIMESTAMP: Critical for time-series analysis and temporal event tracking
Columns
| Column Name | Data Type | Description |
|---|---|---|
| BLOCK_NUMBER | NUMBER | Also known as block height. The block number, which indicates the length of the blockchain, increases after the addition of each new block. |
| BLOCK_TIMESTAMP | TIMESTAMP_NTZ | The date and time at which the block was produced. |
| TX_HASH | TEXT | Transaction hash is a unique 66-character identifier that is generated when a transaction is executed. |
| TX_POSITION | NUMBER | The position of the transaction within the block. |
| EVENT_INDEX | NUMBER | Event number within a transaction. |
| CONTRACT_ADDRESS | TEXT | The address interacted with for a given event. |
| TOPICS | VARIANT | The un-decoded event input topics. |
| TOPIC_0 | TEXT | The first topic of the event, which is a unique identifier for the event. |
| TOPIC_1 | TEXT | The second topic of the event, if applicable. |
| TOPIC_2 | TEXT | The third topic of the event, if applicable. |
| TOPIC_3 | TEXT | The fourth topic of the event, if applicable. |
| DATA | TEXT | The un-decoded event data. |
| EVENT_REMOVED | BOOLEAN | Whether the event has been removed from the transaction. |
| ORIGIN_FROM_ADDRESS | TEXT | The sending address of this transaction. |
| ORIGIN_TO_ADDRESS | TEXT | The receiving address of this transaction. This can be a contract address. |
| ORIGIN_FUNCTION_SIGNATURE | TEXT | The function signature of the contract call that triggered this transaction. |
| TX_SUCCEEDED | BOOLEAN | Whether the transaction was successful, returned as a boolean. |
| FACT_EVENT_LOGS_ID | TEXT | The unique identifier for each row in the table. |
| INSERTED_TIMESTAMP | TIMESTAMP_NTZ | The UTC timestamp at which the row was inserted into the table. |
| MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | The UTC timestamp at which the row was last modified. |