> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allium.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Trades Flagged

### Table Details

| Property | Value |
| - | - |
| Table Name | `ethereum.dex.trades_flagged` |
| Table Status | Production-Ready |
| Unique Key | `transaction_hash`, `unique_id` |
| Clustering Key(s) | `block_timestamp::date` |

### Methodology

[DEX trade flagging methodology is](/historical-data/supported-blockchains/evm/core-schemas/dex/trades-flagged/methodology)

### Table Columns

| Column Name | Data Type | Description |
| - | - | - |
| block\_timestamp | TIMESTAMP\_NTZ(9) | Block timestamp of the swap event. |
| block\_number | NUMBER(38,0) | Block number of the swap event. |
| transaction\_hash | VARCHAR(66) | Transaction hash that this swap belongs to. |
| transaction\_from\_address | VARCHAR(42) | 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(16777216) | The project (decentralized exchange) of the liquidity pool that the swap occurred from. |
| protocol | VARCHAR(16777216) | DEX protocol (& version, if applicable) of the contract address facilitating the swap. |
| liquidity\_pool\_address | VARCHAR(42) | 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)`. |
| \_created\_at | TIMESTAMP\_NTZ(9) | Timestamp of when the entry was created in the database. |
| \_updated\_at | TIMESTAMP\_NTZ(9) | Timestamp of when the entry was last updated in the database. |
| unique\_id | VARCHAR(16777216) | Unique ID of each trade. |

### Related Docs

* [EVM DEX Trades Flagged](/historical-data/supported-blockchains/evm/core-schemas/dex/trades-flagged.md)