The dex.orderflow model provides transaction-level swap data to illustrate DEX transaction volumes through frontends.

The dex.orderflow model aggregates swaps from both dex trades and aggregator trades by the trades.

Within each transaction, all swaps routed by aggregators and executed by pools are rolled up. The USD volume of the swap is determined by the max usd amount within the entire transaction. Volume and swaps executed by dex pools are aggregated in the liquidity details column, while those routed through dex aggregators are in the aggregator details column.

Frontend Labeling Process:
Contract Interaction Analysis

• Allium maintains a comprehensive mapping of: • Telegram bots • MEV contracts • Aggregator routers
• Transactions are labeled based on the contract address they interact with (to_address)
• Example: ParaSwap transactions are identified by interactions with the Augustus Router

Event Log Analysis

• Aggregator event logs often contain frontend source information
• Examples: OpenOcean: Uses referrer field to identify fee recipients and frontend integrators, KyberSwap: Decodes client data logs containing source information (e.g., "Source":"dextools")

Integrator Field Mapping

• The model combines both contract interactions and integrator fields from dex.aggregator_trades
• Uses a coalesce function to determine the most probable frontend label
• Prioritizes explicit frontend indicators from event logs when available