Ez Lending Deposits

​

Description

​

Key Use Cases

• Track deposit flows and liquidity provision patterns across lending protocols
• Analyze user deposit behavior and capital allocation strategies
• Monitor total value locked (TVL) growth and composition in lending markets
• Study protocol adoption and user preferences in the lending ecosystem
• Calculate interest accrual and yield analysis for deposited assets
• Support risk assessment and collateralization analysis

​

Important Relationships

• Related to defi.ez_lending_borrows for analyzing borrowing against deposits
• Related to defi.ez_lending_withdraws for tracking deposit lifecycle completion
• Connects to core.ez_transfers for underlying asset movement verification
• Links to price.ez_prices_hourly for USD valuation and pricing analysis
• Joins with core.fact_transactions for complete transaction context

​

Commonly-used Fields

• block_timestamp: For time-series analysis and deposit timing patterns
• platform, protocol: For protocol-specific analysis and market share tracking
• depositor: For user behavior analysis and whale deposit tracking
• token_address, token_symbol: For asset-specific deposit analysis
• amount, amount_usd: For volume analysis and value-based metrics
• protocol_market: For market-specific utilization and performance analysis

​

Sample Queries

​

Daily deposit volume by protocol

-- Daily lending deposits by protocol
SELECT
    DATE_TRUNC('day', block_timestamp) AS date,
    platform,
    COUNT(DISTINCT tx_id) AS deposit_txns,
    COUNT(DISTINCT depositor) AS unique_depositors,
    SUM(amount) AS tokens_deposited,
    SUM(amount_usd) AS usd_deposited,
    AVG(amount_usd) AS avg_deposit_size
FROM solana.defi.ez_lending_deposits
WHERE block_timestamp >= CURRENT_DATE - 30
    AND amount_usd IS NOT NULL
GROUP BY 1, 2
ORDER BY 1 DESC, 6 DESC;

​

Protocol market share analysis

-- Protocol market share analysis
WITH protocol_totals AS (
    SELECT
        platform,
        SUM(amount_usd) AS total_usd_deposited,
        COUNT(DISTINCT depositor) AS unique_depositors,
        COUNT(*) AS total_deposits
    FROM solana.defi.ez_lending_deposits
    WHERE block_timestamp >= CURRENT_DATE - 90
        AND amount_usd IS NOT NULL
    GROUP BY platform
)
SELECT
    platform,
    total_usd_deposited,
    total_usd_deposited * 100.0 / SUM(total_usd_deposited) OVER () AS market_share_pct,
    unique_depositors,
    total_deposits,
    total_usd_deposited / total_deposits AS avg_deposit_size
FROM protocol_totals
ORDER BY total_usd_deposited DESC;

​

Depositor behavior patterns

-- Depositor behavior patterns
WITH depositor_activity AS (
    SELECT
        depositor,
        COUNT(DISTINCT platform) AS protocols_used,
        COUNT(*) AS total_deposits,
        SUM(amount_usd) AS total_usd_deposited,
        MIN(block_timestamp) AS first_deposit,
        MAX(block_timestamp) AS last_deposit,
        COUNT(DISTINCT DATE_TRUNC('month', block_timestamp)) AS active_months
    FROM solana.defi.ez_lending_deposits
    WHERE amount_usd IS NOT NULL
    GROUP BY depositor
)
SELECT
    CASE
        WHEN total_usd_deposited < 1000 THEN '< $1K'
        WHEN total_usd_deposited < 10000 THEN '$1K-$10K'
        WHEN total_usd_deposited < 100000 THEN '$10K-$100K'
        ELSE '$100K+'
    END AS depositor_tier,
    COUNT(*) AS depositor_count,
    AVG(total_deposits) AS avg_deposits_per_user,
    AVG(protocols_used) AS avg_protocols_used,
    SUM(total_usd_deposited) AS tier_total_usd
FROM depositor_activity
GROUP BY depositor_tier
ORDER BY MIN(total_usd_deposited);

​

Large deposits monitoring (whale activity)

-- Large deposits monitoring (whale activity)
SELECT
    block_timestamp,
    tx_id,
    platform,
    depositor,
    token_symbol,
    amount,
    amount_usd,
    protocol_market
FROM solana.defi.ez_lending_deposits
WHERE amount_usd >= 100000
    AND block_timestamp >= CURRENT_DATE - 7
ORDER BY amount_usd DESC;

​

Weekly deposit momentum

-- Weekly deposit momentum
WITH weekly_deposits AS (
    SELECT
        DATE_TRUNC('week', block_timestamp) AS week,
        platform,
        SUM(amount_usd) AS weekly_usd_deposited,
        COUNT(DISTINCT depositor) AS unique_depositors
    FROM solana.defi.ez_lending_deposits
    WHERE block_timestamp >= CURRENT_DATE - 84
        AND amount_usd IS NOT NULL
    GROUP BY 1, 2
)
SELECT
    week,
    platform,
    weekly_usd_deposited,
    LAG(weekly_usd_deposited) OVER (PARTITION BY platform ORDER BY week) AS prev_week_usd,
    (weekly_usd_deposited / NULLIF(LAG(weekly_usd_deposited) OVER (PARTITION BY platform ORDER BY week), 0) - 1) * 100 AS week_over_week_pct,
    unique_depositors
FROM weekly_deposits
ORDER BY week DESC, weekly_usd_deposited DESC;

​

Columns

• 123456789

• Supports block-level analytics, such as block production rate and transaction throughput.
• Useful for tracing transaction inclusion and block explorer integrations.

• 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.

• 5Nf6Q2k6v1Qw2k3v4Qw5Nf6Q2k6v1Qw2k3v4Qw5Nf6Q2k6v1Qw2k3v4Qw5Nf6Q2k6v1Qw2k3v4Qw

• 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 transfer event within the list of events for a given Solana transaction. Used to order and reference transfers within a transaction. Indexing starts at 0 for the first event.

• 0 (first transfer in the transaction)
• 2 (third transfer in the transaction)

• Enables reconstruction of transfer order and analysis of intra-transaction asset movement.
• Used to join, filter, or segment data for protocol analytics, error tracing, and event sequencing. | | 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.

• 0
• 2

• 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. | | 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.

• “4Nd1mY…”
• “TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA”

• 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. | | EVENT_TYPE | TEXT | A string categorizing the type of event or instruction, such as ‘transfer’, ‘mint’, ‘burn’, or protocol-specific actions.

• ‘transfer’
• ‘mint’
• ‘burn’

• Enables segmentation and filtering of on-chain activity for analytics and dashboards.
• Used to group and analyze protocol-specific actions and user behaviors.

• May be derived from decoded instruction data or protocol-specific logic. | | DEPOSITOR | TEXT | The wallet address of the user who is depositing assets into the lending protocol. This is the lender who supplies liquidity to earn interest and potentially use their deposits as collateral for borrowing.

• SOL
• USDC

• Enables grouping and filtering of transfers by token.
• Supports analytics on asset flows, protocol usage, and user preferences. | | TOKEN_IS_VERIFIED | BOOLEAN | A flag indicating if the asset has been verified by the Flipside team. | | AMOUNT_RAW | NUMBER | Unadjusted amount of tokens as it appears on-chain before decimal precision adjustments are applied. This preserves the exact on-chain representation of the token amount for precise calculations and verification.

• USDC: 50.00 (represents 50 USDC tokens)

• Used to analyze transaction volumes, user activity, and protocol flows.
• Supports aggregation of asset movement for analytics and reporting. | | AMOUNT_USD | FLOAT | The USD value of the transferred amount, calculated using the token price at the time of the transfer. This field enables value-based analytics and comparisons across different tokens.

• 123.45 (represents $123.45 USD)

• Used for tracking transaction volumes, wallet activity, and payment flows in USD terms.
• Supports analytics on large value transfers, protocol revenue, and user behavior. | | EZ_LENDING_DEPOSITS_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. |