Free Order Block Indicators for TradingView

Order block is a trading convention, not a single standardized calculation. One script may require a swing break; another may count consecutive directional candles or apply a minimum price move. A body-only zone and a full high-to-low zone can also produce different retests from the same origin candle.

OHLC candles summarize price movement. They do not identify a participant, an unfilled institutional order, or the reason for a subsequent reversal. Volume or ATR filters can describe activity or price expansion, but cannot turn those observations into proof of institutional buying or selling.

The following is an illustrative rule for a custom detector, not a description of either community script and not a tested trading recommendation. Use standard candles on one symbol and timeframe. Keep these settings fixed while comparing results.

A pivot with three bars to its right cannot be confirmed on the pivot bar. A later structure break can add further delay. Drawing the eventual box back at its origin candle makes that location visible on history, but the box was not available there in real time. Record the confirmation bar separately.

TradingView distinguishes plotting into the past from ordinary changes on an open bar. Waiting for bar close reduces intrabar changes; it does not make a backdated drawing an earlier signal. Compare live observations with the reloaded chart and keep the script version and settings fixed.

For higher-timeframe calculations, an unfinished higher-timeframe candle can change. TradingView documents requesting the previous confirmed value with a one-bar expression offset and lookahead_on as a way to obtain confirmed higher-timeframe data. That introduces delay. A lower-timeframe bar close alone does not confirm the higher-timeframe candle.

Scripts use mitigation to mean different events, including a first touch, midpoint penetration, or a close inside the range. State the actual price comparison instead of assuming that the label has a universal meaning.

For the illustrative specification above, let the frozen zone boundaries be low L and high U. A later closed bar touches the zone when its low is at or below U and its high is at or above L. Mark the first such bar as tested and allow only one first-touch alert. A bullish zone becomes invalid when a bar closes strictly below L; a bearish zone becomes invalid when a bar closes strictly above U. Equality does not invalidate it.

If a bar both touches and invalidates the zone, invalidation takes priority and no first-touch alert fires. A gap beyond the boundary can invalidate a zone without trading inside it. Keep invalidated records visible or logged during evaluation; deleting failed zones can make a historical chart look more successful than the complete event record.

Use the same exchange symbol, session, standard candle type, timeframe, and date interval for each candidate. Write the required behavior before inspecting the results. The checks below evaluate transparency and consistency; passing them does not establish profitability.

Use the detection specification as a brief for Pineify Pine Script AI Coding Agent. Ask for inputs for swing confirmation, displacement, candle search, and zone lifetime, plus separate origin and confirmation labels. Request an event log or visible state changes so that a deleted box does not erase its history from your review.

Review the generated source, run a Pine syntax check, and compare chart behavior against the written rules before relying on alerts. Compilation checks syntax; it does not prove correct trading logic or future returns. Custom code generation is separate from the free community scripts listed here.