Concentrated TRX accumulation in exchange‑linked wallets precedes sell execution
Why it repeats:
Large sellers often aggregate liquidity into custodian or OTC hubs before executing block trades.
This manifests on‑chain as multiple inbound transfers converging to known exchange or OTC addresses over a period of hours to days.
Pattern specifics:
Track clusters of inbound transfers where the number of unique source addresses increases rapidly and cumulative transferred TRX exceeds a threshold relative to typical exchange daily inflows (e.g., >2x median).
Pay attention to temporal clustering (several transfers within a short window) and reuse of destination addresses.
Complementary signals:
Simultaneous growth in exchange orderbook sell volumes, increases in perpetual short OI, and social chatter indicating large holders selling.
For TRXDOWN the expected effect is that as sellers execute, spot TRX faces downward pressure and the inverse token rallies; the staged nature of block execution often creates multiple dips and rebounds that can be harvested with tactical entries.
Detection filters:
Use heuristics to exclude internal rebalancing (transfers between same entity addresses) and cold‑wallet consolidations that are not exchange‑linked.
Validate destination addresses against exchange deposit addresses and OTC custody tags.
Execution:
When a cluster is detected, prepare size schedules and liquidity checks — block sellers may execute iceberg orders or use OTC desks that impact spot gradually.
Risk controls:
Large wallet activity is noisy—some inflows may represent post‑acquisition custody or staking operations that are non‑sell.
Always cross‑check with withdrawal patterns (if large withdrawals follow, it indicates outflows rather than immediate sells).
Monitoring cadence:
Intraday during flow windows, daily for baseline cluster detection.