Skip to main content
IntroArticlesAnalysis
DEFITUNA

Revenue Breakdown by Transaction Type

Displays protocol revenue categorized by transaction operations, revealing which types of activities generate treasury inflows. Transaction types include protocol fees, position management, liquidations, and other revenue-generating operations. Click on a transaction type bar to display the top 10 contributing transactions for that type.

Data​

Loading analytics data...

Use Cases​

This chart helps you:

  • Identify revenue drivers: Understand which protocol operations generate the most income
  • Analyze operation mix: Track the balance between different revenue-generating activities (fees, positions, liquidations)
  • Cross-reference operations: Link transaction types with token and pool breakdowns
  • Investigate specific types: Click bars to examine individual transactions for any transaction type

How to Read This Chart​

Click to expand chart reading guide
  • Bar height: Each transaction type's total revenue contribution in SOL
  • X-axis: Transaction type categories (labels may be truncated for display)
  • Y-axis: Revenue amount in SOL
  • Transaction types: Include protocol fees, position management, liquidations, and other operations
  • Interactions:
    • Click on bars to filter the transaction table below
    • Hover over bars to see exact SOL amounts and type 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)
  • Classification system: Log-based transaction analysis with 100% attribution accuracy
  • Type definitions: Configured pattern matching rules maintained in the backend

For complete pipeline details, see Data Pipeline.

Classification System

All transactions are classified using log-based pattern matching:

  1. Log extraction: Transaction logs contain instruction names from on-chain programs
  2. Pattern matching: Instructions are matched against known patterns in the classification configuration
  3. Type assignment: Each transaction receives exactly one type classification
  4. Revenue filtering: Non-revenue types (staking deposits, system operations) are excluded

The classification engine examines program execution logs to identify transaction purposes. This approach provides deterministic, auditable classification.

Common Transaction Types

  • Protocol Fees: Revenue from fee collection across various operations (e.g. Fusion)
  • Position Management: Income from opening and managing liquidity positions
  • Liquidations: Proceeds from liquidating underwater positions
  • Compound Operations: Fee compounding activities
  • Other Operations: Additional protocol-specific revenue sources

Revenue Filtering

Excluded from revenue totals:

  • Staking operations: User deposits (withdrawable, not revenue)
  • SwapReward transactions: Conversion operations (attribution handled separately)
  • System transactions: Operational overhead

See the revenue attribution system for details on how SwapReward conversions attribute back to original transaction types.

Update Frequency

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

Known Limitations

  • Classification logic updates require historical data reprocessing to maintain consistency
  • New transaction types may initially be classified as "unknown" until patterns are added to the configuration
  • Types with minimal revenue contribution may be grouped into "Other" category
  • Chart shows cumulative data; individual transaction dates available in the table