Skip to main content
Schema: solana.marinade Table: ez_liquidity_pool_actions Type: Base Table

​
Description

This table captures actions for liquidity pools that use either MSOL or MNDE as one of the liquidity pairs, including deposit and withdrawal events. It provides a unified view of liquidity provision activities across multiple DeFi protocols with USD pricing information, enabling comprehensive analysis of liquidity pool participation and token pair dynamics specifically for Marinade Finance ecosystem.

​
Key Use Cases

  • Analyze liquidity provision patterns for MSOL and MNDE pools
  • Track liquidity pool deposits and withdrawals across protocols
  • Monitor liquidity depth and availability for Marinade tokens
  • Study liquidity provider behavior and preferences
  • Support liquidity pool performance and risk analysis

​
Important Relationships

  • Links to marinade.dim_pools for pool metadata and categorization
  • Connects to various silver.liquidity_pool_actions_* tables for platform-specific data
  • References price.ez_prices_hourly for USD price conversion
  • Provides liquidity context for Marinade Finance ecosystem analytics

​
Commonly-used Fields

  • block_timestamp: Essential for time-series analysis and trend detection
  • action_type: Critical for categorizing deposit vs withdrawal activities
  • provider_address: Key for liquidity provider analysis and behavior tracking
  • pool_address: Important for pool-specific analysis and filtering
  • token_a_amount_usd and token_b_amount_usd: Critical for value analysis and financial metrics
  • platform: Key for cross-protocol comparison and platform-specific analysis

​
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 | | 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. | | ACTION_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. | | PROVIDER_ADDRESS | TEXT | The address of the liquidity provider who is performing the deposit or withdrawal action. This field identifies the user providing or removing liquidity from the pool.
  • Data type: STRING (base58 Solana address)
  • Business context: Used to track liquidity providers, analyze provider behavior, and identify active liquidity participants.
  • Analytics use cases: Liquidity provider analysis, provider behavior studies, and liquidity provision tracking.
  • Example: ‘4Nd1mYw4r…’ | | TOKEN_A_MINT | TEXT | Address of the mint representing the first token in a liquidity pool pair | | TOKEN_A_SYMBOL | TEXT | The symbol of asset. | | TOKEN_A_AMOUNT | FLOAT | Amount of the first token in a liquidity pool pair transferred during a liquidity pool action | | TOKEN_A_AMOUNT_USD | NUMBER | The USD value of token A involved in the liquidity pool action, calculated using the token’s price at the time of the action.
  • Data type: NUMBER (float, USD value)
  • Business context: Used to calculate USD-denominated liquidity flows and measure the economic impact of liquidity actions.
  • Analytics use cases: USD liquidity flow analysis, economic impact measurement, and value-based liquidity studies.
  • Example: 150.25 | | TOKEN_B_MINT | TEXT | Address of the mint representing the second token in a liquidity pool pair | | TOKEN_B_SYMBOL | TEXT | The symbol of asset. | | TOKEN_B_AMOUNT | FLOAT | Amount of the second token in a liquidity pool pair transferred during a liquidity pool action | | TOKEN_B_AMOUNT_USD | NUMBER | The USD value of token B involved in the liquidity pool action, calculated using the token’s price at the time of the action.
  • Data type: NUMBER (float, USD value)
  • Business context: Used to calculate USD-denominated liquidity flows and measure the economic impact of liquidity actions.
  • Analytics use cases: USD liquidity flow analysis, economic impact measurement, and value-based liquidity studies.
  • Example: 75.50 | | POOL_ADDRESS | TEXT | The address of the liquidity pool where the action is being performed. This field identifies the specific pool involved in the liquidity action.
  • Data type: STRING (base58 Solana address)
  • Business context: Used to identify specific liquidity pools, analyze pool activity, and track pool-specific liquidity flows.
  • Analytics use cases: Pool-level analysis, liquidity flow tracking, and pool performance studies.
  • Example: ‘4Nd1mYw4r…’ | | POOL_NAME | TEXT | The name of the liquidity pool, typically formatted as a token pair (e.g., “MSOL-USDC”). This field provides a human-readable identifier for the pool, enabling easy identification and analysis of specific liquidity pools.
Data type: STRING (pool name) Business context: Used to identify liquidity pools, analyze pool naming patterns, and provide user-friendly pool references. Analytics use cases: Pool identification, naming pattern analysis, and user interface display. Example: ‘MSOL-USDC’, ‘MNDE-SOL’, ‘MSOL-RAY’ | | IS_MSOL_POOL | BOOLEAN | Whether the pool has MSOL as one of the tokens. This field indicates if the liquidity pool contains Marinade Staked SOL (MSOL) as a trading pair, enabling MSOL-specific pool filtering and analysis. Data type: BOOLEAN (true/false) Business context: Used to filter MSOL-related pools, analyze MSOL liquidity distribution, and track MSOL trading opportunities. Analytics use cases: MSOL pool filtering, liquidity distribution analysis, and trading opportunity tracking. Example: true, false | | IS_MNDE_POOL | BOOLEAN | Whether the pool has MNDE as one of the tokens. This field indicates if the liquidity pool contains Marinade Finance governance token (MNDE) as a trading pair, enabling MNDE-specific pool filtering and analysis. Data type: BOOLEAN (true/false) Business context: Used to filter MNDE-related pools, analyze MNDE liquidity distribution, and track MNDE trading opportunities. Analytics use cases: MNDE pool filtering, liquidity distribution analysis, and trading opportunity tracking. Example: true, false | | PROGRAM_ID | TEXT | The 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, deployments, events, and interface changes.
  • Supports segmentation of activity by protocol, DEX, NFT marketplace, or other on-chain application. | | PLATFORM | TEXT | Name of the liquidity pool protocol or platform. This field identifies the DeFi protocol that hosts the liquidity pool, enabling cross-protocol analysis and platform-specific comparisons.
Data type: STRING (platform name) Business context: Used to categorize pools by protocol, analyze cross-platform liquidity distribution, and compare platform performance. Analytics use cases: Platform categorization, cross-protocol analysis, and performance comparison. Example: ‘raydium’, ‘orca’, ‘meteora’ | | EZ_LIQUIDITY_POOL_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. |