Spike monitor — is flow surging right now, and which way?Per name: the last 5-min change in call vs put volume vs its normal pace at 3 horizons (5m median · 1h avg · 1d avg). ≥3× = SPIKE. Red = calls surging (bullish flow), purple = puts surging (bearish). Each card also carries a mini session strip (a miniature of the big chart below) and shaded pace chips, ALL on one shared scale so the 4 names compare at a glance. Click a card to chart it.
loading…
Flow over timeDiverging bars: calls UP (green) / puts DOWN (red) added each 5-min. A tall bar = a spike (outlined + ▲/▼). Green-vs-red balance = directional bias; switch Show→"directional bias" for the cumulative net, or Show→"put/call ratio" for the P/C line (volume = retail-frenzy, premium$ = where-the-money-leans; >1 = puts lead/bearish, <1 = calls lead/bullish). Shaded = 90-min open/close windows. Dashed = SPX & NAS100.
Compare tickers
Largest single-contract prints — latest scan ↓ ranked by volume÷OISupporting detail (NOT chronological — sorted by how many × a contract's day volume exceeds its open interest = heaviest NEW positioning, mostly 0DTE). The spike monitor + chart above are the time-based read.
loading…
Unusual-print pressure — which name/side keeps getting hit, and whenEvery flagged contract (day volume ≥24× its open interest = heavy NEW positioning) from the banked sessions, summed as premium-$ into 5-min bins. Rows = each name's CALLS and PUTS separately on ONE shared ramp, so cells compare across every row and day. Pale = one small print, dark = heavy stacked prints; black outline = a 30×+ tier-2 print landed in that bin; vertical lines = day boundaries. Hover a cell for the exact $; click for a synced dateline; Y slider = ramp contrast. The Sort buttons reorder the rows by the dateline-SELECTED column (click any cell to pick it; no selection = the latest 5-min bin) — heaviest flagged-$ on top or the reverse.
Sort rows
Telegram alerts (spikes + ≥24×/30× prints): set BFM_TELEGRAM_TOKEN + BFM_TELEGRAM_CHAT in the server's apps/_common/local-only/api_keys.php (@BotFather → token; message bot → getUpdates → chat id). Click ↻ scan now to test. Auto-runs every ~5 min during market hours.
apps2/uoa · SPIKE = last 5-min call/put volume ≥3× its normal pace (shown vs 5m median, 1h avg, 1d avg). Diverging bars show direction; vol/OI table = heaviest new positioning. Both fire Telegram. Massive real-time chains, banked ~5 min. SPX/NAS via decoup/data.php.