PD Arrays & Order Flow Advanced

PB: Propulsion Block

Also known as: PB, propulsion OB, nested order block, stacked order block

What is it?

A propulsion block is an order block that forms inside the range of an earlier order block pointing the same way, so the second zone sits on top of the first and adds thrust to the continuation. The logic is that the original block was never fully consumed. Price leaves the zone, comes back, and instead of trading all the way through it, builds a fresh block in the upper part of the old one before pushing away again.

Live example
The second block forms inside the first, 22 pips higher EUR/USD 1H
Price never reached the original 1.0790 low; a fresh block formed at 1.0812 inside it and propelled the move. The risk line stays at the older zone. Illustrative figures.

That shallower reaction is the tell: buyers were willing to act before price reached the original level. On EUR/USD, a bullish block at 1.0790-1.0834 that later hosts a second block at 1.0812-1.0828 inside it is a propulsion block - the reaction now starts 22 pips higher than it did on the first test. Practically, the propulsion block is the level you actually trade and the original block is the level that defines your invalidation.

That combination is why traders like the structure: the entry is tighter than the original zone allows, while the risk still sits behind the older, better-established level. The cost is that a shallow entry gets skipped whenever price decides to take the deeper level first.

Why it matters: A propulsion block marks where a trend accelerates from a shallower level than the original zone, giving a tighter entry with the older block behind it as risk.

Trade impact: Medium

It sets entry precision rather than direction - a tighter entry improves the reward-to-risk but is skipped more often than the deeper zone.

Real-world example

A bullish EUR/USD block at 1.0790-1.0834 was retested only to 1.0812, where a second block formed at 1.0812-1.0828 inside it and price propelled to 1.0906 without revisiting the original low.

How SignalBots handles it

SignalBots publishes the entry level with the stop distance attached, so a tighter propulsion entry is sized on its own risk rather than on the wider zone behind it. See /risk-warning.

Pro tip

Keep the invalidation at the original block's far edge even when you enter at the propulsion block - the shallower zone is the entry, not the risk boundary.

Common pitfalls

Tightening the stop to the propulsion block itself, which puts it inside the older zone where price routinely trades before continuing.

FAQs

Frequently asked questions

How do I tell a propulsion block from a normal order block?

By where it sits. A propulsion block forms inside the price range of an existing block facing the same direction. If the new block sits outside the old one, it is simply the next order block, not a propulsion block.

Does it have to be on the same timeframe?

Not necessarily. A common read is a daily block hosting a 1-hour block inside it, which is where the entry precision comes from. The higher-timeframe zone stays the risk boundary in that case.

What invalidates a propulsion block?

A close beyond the original block, not beyond the propulsion block. Price trading down through the shallow zone into the deeper one is ordinary behaviour and does not end the setup.

Is the propulsion block a stronger signal than the original?

It is a more precise one, not a more reliable one. It gives a better entry price when it works and gets missed entirely when price goes for the deeper level, so the trade-off is fill rate against reward-to-risk.

Can propulsion blocks stack more than twice?

They can, and each layer sits a little higher in a rising market. Beyond two or three the structure usually says more about how strong the trend is than about where to enter, and capital is still at risk on every one.

Trading involves substantial risk of loss. Historical and backtested results do not guarantee future performance. Read the full risk warning.

Add SignalBots as a preferred source on Google Add SignalBots as a preferred source on Google