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

​
Description

This table contains swaps involving MSOL and MNDE tokens across multiple decentralized exchanges and aggregators. It provides a unified view of trading activities for Marinade Finance tokens with USD pricing information, enabling comprehensive analysis of token liquidity and trading patterns.

​
Key Use Cases

  • Analyze MSOL and MNDE trading volume and patterns
  • Track token liquidity across different DEX platforms
  • Monitor trading activity and price impact
  • Study user trading behavior and preferences
  • Support token economics and market analysis

​
Important Relationships

  • Links to defi.fact_swaps_jupiter_summary for Jupiter aggregator swaps
  • Connects to silver.marinade_swaps for direct DEX swaps
  • References price.ez_prices_hourly for USD price conversion
  • Connects to core.dim_labels for platform identification
  • Provides trading context for Marinade Finance ecosystem analytics

​
Commonly-used Fields

  • block_timestamp: Essential for time-series analysis and trend detection
  • swapper: Key for user analysis and trading behavior tracking
  • swap_from_mint and swap_to_mint: Critical for token pair analysis and filtering
  • swap_from_amount_usd and swap_to_amount_usd: Important for value analysis and financial metrics
  • platform: Key for cross-platform comparison and DEX analysis

​
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 ‘block_id’ share the same ‘block_timestamp’. | | 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 | | | INNER_INDEX | NUMBER | | | SUCCEEDED | BOOLEAN | | | SWAPPER | TEXT | The Solana address (base58-encoded string) that initiated the swap transaction. This field identifies the user or contract responsible for the swap, enabling wallet-level analytics, behavioral segmentation, and user journey analysis.
  • Data type: STRING (base58 Solana address, e.g., 4Nd1mYw4r...)
  • Business context: Used to group swaps by user, analyze trading patterns, and track protocol adoption.
  • Analytics use cases: User segmentation, whale tracking, protocol adoption analysis, and cross-table joins with other user-activity models.
  • Example: 4Nd1mYw4r... | | SWAP_FROM_MINT | TEXT | The mint address of the token being sent or swapped from in the transaction. This is a unique identifier for the SPL token or SOL.
  • Data type: STRING (base58 Solana mint address)
  • Business context: Used to identify the source asset in the swap, filter by token, and analyze token-specific activity.
  • Analytics use cases: Token flow analysis, asset popularity studies, and cross-token comparisons.
  • Example: SOL: So11111111111111111111111111111111111111112, USDC: Es9vMFrzaCER... | | SWAP_FROM_SYMBOL | TEXT | The symbol of the token being sent or swapped from in the transaction. This field provides a human-readable identifier for the source asset, enabling token-specific analytics and filtering.
  • Data type: STRING (e.g., ‘SOL’, ‘USDC’, ‘RAY’)
  • Business context: Used to identify the source asset in the swap, filter by token, and analyze token-specific activity.
  • Analytics use cases: Token flow analysis, asset popularity studies, and cross-token comparisons.
  • Example: ‘SOL’ | | SWAP_FROM_AMOUNT | FLOAT | The total amount of the token sent in to initiate the swap, as recorded on-chain. This value is already decimal adjusted according to the token’s standard decimals, and represents the human-readable amount.
  • Data type: NUMBER (float or integer, depending on token)
  • Business context: Used to calculate swap volume, analyze liquidity flows, and measure user activity.
  • Analytics use cases: Volume analysis, liquidity tracking, slippage calculations, and DEX protocol comparisons.
  • Example: For SOL, a value of 2.5 means 2.5 SOL. For USDC, a value of 100.5 means 100.5 USDC. | | SWAP_FROM_AMOUNT_USD | FLOAT | The USD value of the tokens being sent into the swap, calculated using the token’s price at the time of the swap. This field enables USD-denominated volume analysis and value flow tracking.
  • Data type: NUMBER (float, USD value)
  • Business context: Used to calculate USD swap volume, analyze value flows, and measure economic impact of swaps.
  • Analytics use cases: USD volume analysis, value flow tracking, and economic impact measurement.
  • Example: 150.25 | | SWAP_TO_MINT | TEXT | The mint address of the token being received or swapped to in the transaction. This is a unique identifier for the SPL token or SOL.
  • Data type: STRING (base58 Solana mint address)
  • Business context: Used to identify the destination asset in the swap, filter by token, and analyze token-specific inflows.
  • Analytics use cases: Token inflow analysis, asset demand studies, and DEX routing analytics.
  • Example: SOL: So11111111111111111111111111111111111111112, USDT: BQvQ8... | | SWAP_TO_SYMBOL | TEXT | The symbol of the token being received or swapped to in the transaction. This field provides a human-readable identifier for the destination asset, enabling token-specific analytics and filtering.
  • Data type: STRING (e.g., ‘USDC’, ‘SOL’, ‘RAY’)
  • Business context: Used to identify the destination asset in the swap, filter by token, and analyze token-specific inflows.
  • Analytics use cases: Token inflow analysis, asset demand studies, and DEX routing analytics.
  • Example: ‘USDC’ | | SWAP_TO_AMOUNT | FLOAT | The total amount of the token received from the swap, as recorded on-chain. This value is already decimal adjusted according to the token’s standard decimals, and represents the human-readable amount.
  • Data type: NUMBER (float or integer, depending on token)
  • Business context: Used to measure swap output, analyze price impact, and track liquidity received.
  • Analytics use cases: Output volume analysis, slippage and price impact studies, and DEX performance comparisons.
  • Example: For USDC, a value of 1.0 means 1 USDC. For SOL, a value of 0.25 means 0.25 SOL. | | SWAP_TO_AMOUNT_USD | FLOAT | The USD value of the tokens being received from the swap, calculated using the token’s price at the time of the swap. This field enables USD-denominated output analysis and value flow tracking.
  • Data type: NUMBER (float, USD value)
  • Business context: Used to calculate USD output volume, analyze value flows, and measure economic impact of swaps.
  • Analytics use cases: USD output analysis, value flow tracking, and economic impact measurement.
  • Example: 148.75 | | 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 decentralized exchange used to perform the swap. This field identifies the specific DEX or aggregator platform that facilitated the swap, enabling cross-platform analysis and platform-specific comparisons.
Data type: STRING (platform name) Business context: Used to categorize swaps by platform, analyze cross-platform trading patterns, and compare platform performance. Analytics use cases: Platform categorization, cross-platform analysis, and performance comparison. Example: ‘Jupiter’, ‘Raydium’, ‘Orca’, ‘Meteora’ | | MARINADE_EZ_SWAPS_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. |