Skip to main content
IntroArticlesAnalysis
DEFITUNA

Revenue Breakdown by Pool

Displays protocol revenue categorized by liquidity pool, showing which LP positions generate treasury inflows. Revenue currently comes from Orca Whirlpools or Fusion pools. Click on a pool bar to display the top 10 contributing transactions for that pool.

Data​

Loading analytics data...

Use Cases​

This chart helps you:

  • Assess pool concentration: Determine if revenue is driven by specific pools or venues
  • Cross-reference pool activity: Link pool data with token and transaction type breakdowns
  • Investigate specific pools: Click bars to examine individual transactions for any pool

How to Read This Chart​

Click to expand chart reading guide
  • Bar height: Each pool's total revenue contribution in SOL
  • X-axis: Pool identifiers (labels may be truncated for display)
  • Y-axis: Revenue amount in SOL
  • Pool types: Primarily Orca Whirlpools and Fusion pools, with "Other" representing unattributed revenue
  • Interactions:
    • Click on bars to filter the transaction table below
    • Hover over bars to see exact SOL amounts and pool names
    • Transaction signatures in the table link to Solscan for detailed exploration

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:

  1. Direct address matching: Compares transaction account addresses against a registry of known pool addresses
  2. Alias resolution: Maps alternative addresses (position accounts, vault accounts) to canonical pool IDs
  3. Token pair hints: Uses mint addresses involved in transfers to identify pools when direct matches aren't found
  4. Protocol detection: Identifies the protocol (Orca, Fusion, etc.) from program IDs to generate fallback labels

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

Pool Labeling

Pool addresses are mapped to human-readable names:

  • Manual labels: Hand-curated names for major pools (e.g., "Orca SOL-USDC Whirlpool")
  • Auto-generated: Programmatic labels for unlabeled pools (e.g., "Orca pool abc1...def2")
  • Unknown pools: Placeholder labels for newly discovered pools

When new pools are encountered, they receive generated labels and can be promoted to the manual registry with proper names.

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., WSOL-USDC, USDC-TUNA)

Integration with Revenue Attribution

Pool attribution occurs during revenue processing:

  • Each transaction attributed to exactly one pool
  • Pool + transaction type combinations tracked for detailed analysis
  • Enables pool-specific revenue breakdowns

Update Frequency

Data is automatically updated once a 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
  • Pools with minimal revenue contribution may be grouped into "Other" category
  • Chart shows cumulative data; individual transaction dates available in the table
  • Unlabeled pools receive generated labels until the pool registry is updated