Aggregates swaps from both dex.trades and dex.aggregatortrades by transactionhash, showing the dex aggregator(s) and underlying liquidity sources used in a single transaction.
| Blockchains Supported | Projects | Protocols | Tables |
|---|---|---|---|
ethereum polygon arbitrum optimism bsc base scroll mode | Protocols supported in dex.trades and dex.aggregator_trades | Protocols supported in dex.trades and dex.aggregator_trades | dex.orderflow dex.unhydrated_orderflow |
The dex.orderflow model aggregates swaps from both dex.trades and dex.aggregatortrades by transactionhash. Within each transaction, all swaps routed by aggregators and executed by pools are rolled up. The usdvolume of the swap is determined by the max usdamount within the entire transaction. Volume and swaps executed by dex pools are aggregated in the liquiditydetails column, while those routed through dex aggregators are in the aggregatordetails column.
Frontend labeling is done by mapping key routers and aggregator routers to label the transaction by the most probable frontend. The labeling process involves identifying the contract the user interacted with, which could be a meta_aggregator, aggregator, router, or direct liquidity pool interaction. The coalesce function is used to select the most probable frontend label.