Trade What Others
Can’t See

HiddenTrades Pro is a multi-timeframe zone engine for TradingView. It identifies Breaker Blocks (BB) and Hidden Order Blocks (HOB), checks them against automatically anchored Fibonacci retracements, combines overlapping areas into clusters and communicates changes through one consolidated alert setup.

From order block to confirmed zone

Detection starts with a potential order block: a candle whose body is later crossed in the opposing direction. It becomes a BB/HOB only when displacement and a qualifying chain of Fair Value Gaps confirm the break. The displacement candle begins the sequence but is not counted as an FVG.

The label’s multiplier reflects the number of qualifying gaps. A single-gap zone may read “15m”; additional gaps produce “2x 15m”, “3x 15m” and higher counts. Scanning continues after confirmation, so an existing zone can gain a higher strength count later.

Mitigation that preserves untouched price areas

One Partial Mitigation percentage governs tolerance throughout formation and the live zone’s lifecycle. Its default is 5%, covering displacement wicks, FVG and crossing candles that open inside the order block, overlap before confirmation and mitigation after confirmation.

When price trades into a zone, the affected edge is trimmed while the untouched remainder survives. Either side can be trimmed. A “p” identifies partial mitigation, with an optional tracked percentage such as “p (12%)”. Setting the input to zero applies strict behaviour: no wick overlap during formation and no zone survival after mitigation.

The engine scans the chart timeframe alongside up to 40 external intervals. Supported selections span 1 minute to 3 hours, 4 to 23 hours, and daily through 12-month intervals in bundles. Unconventional intervals include 35, 89, 96, 144, 216, 233, 288 and 432 minutes. If your selection exceeds the cap, the highest timeframes are dropped first.

Three ways to select your timeframes

• Auto selects a neighbourhood of lower and higher intervals around the chart timeframe.
• Auto from Selected builds that neighbourhood using only the intervals you have enabled.
• Selected Only follows your checked selections exactly.

Clusters instead of overlapping clutter

Positive price overlap always merges zones. Nearby zones can also join when they fall within the “Merge nearby BBs into Cluster (%)” allowance, measured against the established cluster’s height. Only one near merge is permitted per lineage; real price overlap is not subject to that restriction. A cluster appears as a single box with one label listing its member timeframes.

An optional ICT order block layer adds active impulse order blocks alongside BB/HOB zones or displays them on their own. Choose a two- or three-candle impulse requirement, and optionally restrict the layer to order blocks overlapping a breaker zone or cluster.

Body-size filters provide separate minimums for lower timeframes from 1 minute to 3 hours, middle timeframes from 4 to 23 hours and everything above. The strict order block pivot filter lets you set left and right pivot candles, compare bodies or wicks, require an optional preceding same-direction candle, and choose strict directional colours or a flexible neighbour check.

Using only strict pivot order blocks changes side ownership: swing lows own bullish structures and swing highs own bearish ones. The Multi-FVG-only option removes single-FVG zones from both the display and alert output.

A displacement candle can open within or beyond the order block if it closes outside on the expected side and respects the wick tolerance. A full gap across an order block can establish a zone at 1x, but cannot upgrade an existing zone to Multi-FVG status.

For each breaker zone, AutoFib studies nearby swings, selects anchors that explain the structure and measures whether the swing’s Golden Pocket overlaps the zone. This is structural confluence, not a prediction that price will react.

Anchor selection and swing requirements

You may require a swing to break structure (BOS) before it qualifies, and require the BOS level to sit beyond the zone. If no candidate meets the rules, an optional fallback accepts the best non-BOS swing. End anchors can be restricted to structural higher-high and lower-low pivots.

Multi-leg anchoring extends a measurement through later pivots to a configurable depth, optionally requiring an intermediate retracement of a minimum percentage of the complete swing. Near-equal highs or lows beside an anchor can generate double-top or double-bottom alternatives. Their tolerance uses the average candle range at the anchor multiplied by a configurable factor. Minimum swing size can be expressed as an ATR multiple, a percentage move or left unrestricted.

Golden Pocket, scale and result ranking

The Golden Pocket is the tested level. Optional dotted confluence lines show 0.5, 0.705, 0.786 and 0.886, with linear, logarithmic or both price scales available. Multi-FVG zones normally generate one Fibonacci set per FVG pierce from the first gap onward, each with its own reference candle.

Strict results that satisfy all rules rank above BOS-fallback results, which rank above provisional ones. Same-polarity and opposite-polarity hits are tracked separately. A HIT means that a qualifying swing’s Golden Pocket lands on the zone within tolerance; it does not imply that the zone will hold.

Boxes, swing lines and status labels can be hidden independently without disabling numeric calculations. By default, AutoFib calculates only on the last bar and refreshes on realtime bar close to keep computational demand predictable. Historical bars therefore do not each retain their own separate Fibonacci evaluation.

Enable alerts in the indicator, choose the events you want and create one TradingView alert with “Any alert() function call”. All further controls live in the indicator settings. Each event line reports the side, the count and timeframe, then the price range.

Event categories cover NEW BB/HOB, DELAYED NEW BB/HOB, BB/HOB CHANGED, BB/HOB REMOVED, CLUSTER CHANGE, NEAR and TOUCH. Choose Both, Long or Short direction, and include all events or cluster events only. Newly confirmed zones can be delayed by zero to ten source-timeframe candles.

Control the detail and message volume

Combined grouping minimises messages, Separate sections splits updates by category and Every event sends individual updates. Payloads are split without losing content below the 40,000-character limit, then delivered first-in, first-out at up to 14 calls per 180 seconds. Remaining events wait for later realtime ticks. Minimum cluster size can restrict notifications to zones in clusters of at least two, three, four or five members.

A near-price alert fires once when price crosses from outside the chosen percentage distance into a zone’s or cluster’s proximity area. A second notification at half the distance is optional. A newly discovered zone already near price does not immediately trigger, and price already inside a zone does not generate a near event. First-touch alerts can be enabled separately.

Individual switches cover mitigation, FVG count changes, direction conversions, cluster membership, cluster boundaries and labels, dissolution and zone removal. ICT order block confluence can be appended as “| OBs: ...” or “| OB cluster: ...”. Those order blocks never trigger standalone alerts.

Display controls

Boxes and labels cover the chart timeframe and selected external intervals within TradingView’s ceiling of 500 boxes and 500 labels. Adjust label size, bold text, colours and separate offsets for individual zones and clusters. Up to three nearby labels can merge to reduce clutter, while recently removed zones may remain visible in grey for a chosen number of bars.

“Hide live mitigated BBs/HOBs” previews mitigation on the forming candle, including FVG exemptions and deferred split touches, and hides zones that fail that preview. It may change before the candle closes, but never changes confirmed state.

Start with a standard candlestick chart

1. Add HiddenTrades Pro to your chart.
2. Begin with Auto timeframe selection, or use Selected Only to choose the intervals you trade.
3. Treat Multi-FVG zones and clusters as areas to evaluate your own entry criteria. The far edge can provide a structural invalidation reference.
4. Enable your preferred alert events and create one alert using “Any alert() function call”. Combined grouping keeps message volume lowest.

Published chart defaults

The published setup uses 10,000 candles of history, a 500-candle breaker formation window, 5% Partial Mitigation, BBs/HOBs as the MTF display mode, and Auto selection with 20 lower and 20 higher timeframes. Nearby-cluster merging is set to 15%. Optional filters and alerts start disabled.

External timeframe requests use lookahead_off and gaps_off, so future data does not enter closed bars and historical zones do not repaint. Higher-timeframe zones arrive only when their source candle closes. On a one-minute chart, a new four-hour zone can therefore appear up to four hours after its order block candle. That delay reflects higher-timeframe data delivery.

The live mitigation preview can change during a forming candle and settles at its close without rewriting confirmed history. Available history depends on the bars loaded and your TradingView plan. Higher timeframes need enough history to form zones, while large timeframe selections with live previews can hit runtime or memory limits. Reduce the timeframe count or history depth if needed.

Use standard candlesticks. Heikin Ashi, Renko, Kagi, Point and Figure, and Range charts supply synthetic prices that make the resulting zones unsuitable for this analysis. Different settings can materially change the display, confirmation-based structures can arrive only after the required candle or pivot confirms, and choppy or low-liquidity markets may produce more zones.

Original implementation, protected source

Order blocks, Fair Value Gaps and breaker blocks are public concepts. This is original code, not a modification of a published script. Its implementation combines displacement-led gap chains, a shared tolerance budget across formation and mitigation, two-sided trimming that preserves untouched zones, and a cluster model allowing unrestricted real overlap but only one nearby merge per lineage.

The detection chain and tolerance model are the core of the work, which is why the source remains protected. The documented inputs, detection rules, alert format and limitations let users evaluate the behaviour without source access.