Trades Flagged - Allium Documentation Hub

The dex.trades_flagged table contains trades from dex.trades flagged as wash or otherwise inorganic, one row per trade, from the flag registry or the wash heuristics. Rows are not removed from dex.trades; dex.trades_enriched marks them with is_flagged. Available on Arbitrum, Base, BSC, Ethereum and Robinhood.

Methodology

Adjusted Volume

Flagged trades stay in dex.trades. To get volume without them:

Trade level: use sum(usd_amount_adjusted) from dex.trades_enriched.
Daily metrics: use the *_adjusted columns in metrics.overview, such as dex_volume_usd_adjusted, and total_volume_usd_adjusted in crosschain.metrics.dex_overview. The columns without _adjusted stay raw.

For the release notes, see DEX wash flags on 5 chains.

Table Columns

Unique Key: transaction_hash, unique_id

Column Name	Data Type	Description
block_timestamp	TIMESTAMP_NTZ(9)	Block timestamp of the swap event.
block_number	BIGINT	Block number of the swap event.
transaction_hash	VARCHAR	Transaction hash that this swap belongs to.
transaction_from_address	VARCHAR	Transaction sender address. I.e. the address of the transaction initiator. (from_address in the raw.transactions field for the transaction_hash of this swap).
project	VARCHAR	The project (decentralized exchange) of the liquidity pool that the swap occurred from.
protocol	VARCHAR	DEX protocol (& version, if applicable) of the contract address facilitating the swap.
liquidity_pool_address	VARCHAR	Contract address of the liquidity pool holding the asset. For protocol without the concept of LP such as airswap, this will be null.
flagged_details	VARIANT	Why the trade is flagged, as one object. `reason`: the highest-priority match. `source`: what matched it, a registry key (`transaction_hash`, `transaction_from_address`, `transaction_to_address`) or `heuristic`. `flagged_at`: the registry entry’s date, or the date a heuristic first flagged the trade; it is not the date the change reached production. `reasons`: every match, in priority order. Each reason key holds a list of its matches, each with its own `flagged_at`. `supply_shock_v1` / `self_issued_v1` = the trade touches a flagged token: `token_address`, `token_flagged_at`, `flagged_value` (units over pre-shock supply, or the creator’s share of legs). `same_pool_roundtrip_v1` = the transaction trades one pool both ways and its flow cancels out: `pool_key`, `score` (1 = perfect round trip), `has_liquidity_event`. `roundtrip_wash` (registry): `source`, `value`. Examples: `flagged_details:reason::varchar`; one rule: `array_contains('same_pool_roundtrip_v1'::variant, flagged_details:reasons)`.
unique_id	VARCHAR	Unique ID of each trade.

EVM

​Methodology

​Adjusted Volume

​Table Columns

Methodology

Adjusted Volume

Table Columns