Skip to main content

By Pool

Protocol revenue over time, broken down by liquidity pool. Click a pool in the legend or chart to filter the transactions table.

Data

Loading analytics data...

Use Cases

This chart helps you:

  • Assess pool concentration: Determine if revenue is driven by specific pools or broadly distributed
  • Track trends over time: See how individual pool contributions change day-to-day
  • Compare pool performance: Toggle between daily and cumulative views to spot growing or declining pools
  • Cross-reference pool activity: Link pool data with By Type and Pools vs. Types breakdowns
  • Investigate specific pools: Click a pool in the legend to isolate it and examine its top transactions

How to Read This Chart

Click to expand chart reading guide
  • Daily view (stacked bars): Each bar segment shows a pool's daily revenue in SOL. The total bar height is the sum across all pools for that day.
  • Cumulative view (stacked area): Each band shows a pool's running total revenue over time. The top of the chart represents total cumulative revenue.
  • Legend: Lists the top 8 pools by total revenue plus an "Others" bucket. Click a pool name in the legend to toggle its visibility.
  • Colors: Each pool has a consistent color across daily and cumulative views.
  • Interactions:
    • Click a bar/area segment to isolate that pool (click again to restore all)
    • Click legend items to show/hide individual pools
    • Hover over the chart to see per-pool and total SOL values (daily values in daily view, running totals in cumulative view)
    • Selected pools also filter the transactions table below

Methodology

Click to expand technical details

Data Sources

  • Treasury transactions: On-chain data from DefiTuna treasury PDA (G9XfJoY81n8A9bZKaJFhJYomRrcvFkuJ22em2g8rZuCh)
  • Pool attribution: Multi-source matching system (registry lookups + auto labels) reconciled against the revenue totals described in Data Quality; flows that cannot be confidently matched remain in "Other" until labeled
  • Pool labels: Automatically created and manually curated pool names maintained in the backend

For complete pipeline details, see Data Pipeline.

Pool Attribution System

Pools are identified through a multi-source matching system:

  • Direct address matching: Compares transaction account addresses against a registry of known pool addresses
  • Alias resolution: Maps alternative addresses (position accounts, vault accounts) to canonical pool IDs
  • Token pair hints: Uses mint addresses involved in transfers to identify pools when direct matches aren't found
  • Protocol detection: Uses each pool's known protocol (Orca, Fusion, etc.) to generate fallback labels when no manual name exists

This hybrid approach ensures comprehensive coverage while maintaining accurate, user-friendly pool names.

Top-N Grouping

The chart displays the top 8 pools ranked by total SOL revenue. All remaining pools are aggregated into an "Others" bucket. This grouping is computed client-side from the summary ranking and applied to the daily time-series data.

Common Pool Types

  • Orca Whirlpools: Concentrated liquidity pools on the Orca DEX (e.g., SOL-USDC, SOL-CBBTC)
  • Fusion Pools: DefiTuna's native liquidity pools (e.g., SOL-USDC, SOL-TUNA)

Update Frequency

Data is automatically updated once per day. Check the "Last updated" timestamp in the site header for data freshness.

Known Limitations

  • Pool labels may show addresses for newly discovered pools until manual names are added
  • The "Others" bucket aggregates all pools outside the top 8, which may include meaningful individual pools
  • The "Other / Not Applicable" named pool represents system-level or unattributed revenue (e.g., direct transfers, protocol operations). It appears inside the top-8 series if it ranks high enough, otherwise it is included in the "Others" aggregation bucket