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

​
Description

This table contains information on liquidity pools that involve MNDE or MSOL tokens as one of the liquidity pairs across multiple DeFi protocols including Raydium, Orca, and Meteora. It serves as a dimensional table providing comprehensive pool metadata, token information, and platform categorization for Marinade Finance ecosystem analysis.

​
Key Use Cases

  • Analyze liquidity pool distribution across different DeFi protocols
  • Track MSOL and MNDE token liquidity availability and depth
  • Monitor pool initialization and creation patterns
  • Support cross-protocol liquidity analysis and comparison
  • Enable pool performance analysis and token pair tracking

​
Important Relationships

  • Links to marinade.ez_liquidity_pool_actions through pool addresses for action analysis
  • Connects to marinade.ez_swaps through pool addresses for swap activity tracking
  • References price.ez_asset_metadata for token symbol and metadata information
  • Provides pool context for Marinade Finance ecosystem analytics

​
Commonly-used Fields

  • pool_address: Essential for linking to pool actions and swaps
  • pool_name: Key for human-readable pool identification and analysis
  • token_a_mint and token_b_mint: Critical for token pair analysis and filtering
  • platform: Important for cross-protocol comparison and platform-specific analysis
  • is_msol_pool and is_mnde_pool: Key for Marinade-specific pool filtering and analysis

​
Columns

Column NameData TypeDescription
POOL_ADDRESSTEXTThe 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’ | | POOL_TOKEN_MINT | TEXT | Address of the liquidity pool token mint | | 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_ACCOUNT | TEXT | Address of the account containing the first token in a liquidity pool pair | | 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_ACCOUNT | TEXT | Address of the account containing the second token in a liquidity pool pair | | INITIALIZED_AT_BLOCK_ID | NUMBER | A 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’. | | INITIALIZED_AT_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). | | INITIALIZED_AT_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 | | INITIALIZED_AT_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. | | INITIALIZED_AT_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. | | 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’ | | DIM_POOLS_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. |