Options Sweeps vs Blocks: What the Prints Actually Show
In options-flow feeds, a sweep label usually describes rapid execution across venues or prices; a block label usually highlights a large print. Neither establishes trader intent.
Separate the execution record from the provider label. An Intermarket Sweep Order (ISO) has a specific routing meaning, while a vendor may group several prints into one sweep alert. A large single print does not prove a privately negotiated institutional bet. Compare contract, execution time, venue, size, premium and trade conditions before interpreting either label.
How to Get Started
Identify the record and its clock
Record the exact option contract, date, timezone and whether the row is an execution or an aggregated alert. Keep execution, report, alert creation and retrieval times separate.
Reconcile the underlying executions
Check unique trade IDs, venues, conditions and any corrections. Sum contract size and price × size × multiplier across eligible prints. Record the grouping window rather than assuming that rows in the same second share a parent order.
Test the side and strategy interpretation
Compare each fill with a valid quote at execution time. Check complex-order flags and related strikes or expirations. Leave direction unresolved when quote timing, trade linkage or opening versus closing information is missing.
Sweep, ISO and block describe different evidence
A sweep-to-fill execution can seek liquidity on several exchanges, producing several prints. That pattern is consistent with rapid execution, but nearby prints can also belong to different customers. A provider grouping them into one row is making an association; the row itself is not a public parent-order identifier.
An ISO is more specific. The Cboe options rules filed with the SEC define a limit order accompanied, as necessary, by orders routed against the full displayed size of better-priced protected quotations. The submitting participant bears the routing responsibility. An ISO designation concerns order handling and price protection, not a forecast, trader identity or minimum premium. Several same-second fills alone do not establish that designation.
A block label on a retail flow feed generally identifies size concentrated in a print. Its size or premium cutoff is provider-specific; do not apply a universal 100-contract or $500,000 definition. The print may come from an auction, a cross, floor execution or another permitted mechanism. Size alone cannot prove which one, whether the trade was negotiated, or whether it was institutional. Read the actual execution conditions. A large ISO execution can also meet a vendor's block-size screen, so these categories need not be mutually exclusive.
- Sweep pattern: examine venues, prices, timestamps and the grouping rule.
- ISO condition: examine the reported order or trade designation, not just the number of prints.
- Block-size label: examine the provider threshold and original print size; it does not identify a strategy.
Rebuild a sweep candidate from three executions
This is a hypothetical teaching dataset, not a recorded market event. All three executions concern XYZ, November 20, 2026 expiry, $100 call, with a standard 100 multiplier. Times are October 16, 2026 in America/New_York. Assume distinct source trade IDs, no cancellations and comparable execution clocks. Venue names illustrate fragmentation only.
| ID / execution time | Venue | Contracts | Price | Gross premium |
|---|---|---|---|---|
| A / 10:00:00.100 | Cboe | 200 | $2.00 | $40,000 |
| B / 10:00:00.130 | Nasdaq ISE | 150 | $2.01 | $30,150 |
| C / 10:00:00.180 | MIAX | 250 | $2.02 | $50,500 |
Total size = 200 + 150 + 250 = 600 contracts. Gross premium = (200 × $2.00 + 150 × $2.01 + 250 × $2.02) × 100 = $120,650, excluding fees. The size-weighted price is $120,650 / (600 × 100) = $2.010833. Multiplying the rounded display price of $2.01 by 600 × 100 gives $120,600, a $50 rounding difference. Check the contract multiplier before applying this formula to adjusted options.
The first-to-last execution span is 80 milliseconds. A hypothetical 100-millisecond grouping rule might combine them if its other criteria match. A $100,000 minimum applied after aggregation keeps the $120,650 group; applied to each print first, it removes all three. Unusual Whales documents this filter-order effect and describes grouping transactions that are likely related. It does not make the association certain. Neither the example window nor these venues are Pineify detection parameters.
For comparison, suppose a separate 600-contract print executes at 10:01:00.000 on Cboe at $2.01, for $120,600. It has nearly the same premium and may meet a vendor's block-size threshold. That single line provides no evidence of a negotiation, slower intent or a longer holding period.
Late reports and corrections change the aggregate
Suppose print C executed at 10:00:00.180 but reached the feed at 10:00:02.500. An alert built at 10:00:00.300 might initially contain only A and B: 350 contracts and $70,150. A later revision could contain all 600 contracts and $120,650. A report-time grouping window could instead place C in a different group. Record the aggregation cutoff and whether past alerts are revised before comparing two screenshots.
A duplicated delivery of B is not another 150 contracts. Counting it twice inflates the example to 750 contracts and $150,800. If B is subsequently corrected from 150 to 100 contracts, the revised total is 550 contracts and $110,600. Replace the affected record according to the source correction protocol; do not count the original and correction as two new trades.
- Deduplicate with source identifiers and correction links. Equal time, price and size can still describe two legitimate executions.
- Keep execution and receipt timestamps separately. A newly received late print does not establish new buying at that moment.
- Check cancellations, out-of-sequence and complex-order conditions before aggregation. Missing fields should remain unknown.
- An alert can overlap another alert on the same contract. Adding alert totals is unsafe without the constituent trade sets.
Bid/ask location is a side estimate, not a trading thesis
For print A, assume a valid NBBO of $1.98 bid / $2.00 ask immediately before execution. The $2.00 fill is at the ask, consistent with a buyer initiating against the offer. If the quote moves to $2.02 / $2.04 before a delayed report arrives, matching the same $2.00 fill to that later quote makes it appear below bid. That classification reversal comes from quote timing, not a change in the executed trade.
Use quotes available at the execution timestamp with known sequencing and timestamp precision. Check spread width, locked or crossed quotes, stale quotes and report conditions. A midpoint fill remains ambiguous. An above-ask print does not by itself prove a sweep, and a sweep does not require every fill to be above ask. Unusual Whales explains its side labels as an inference from execution price relative to bid and ask.
Even a correctly inferred call purchase may close a short call, hedge short stock or form one leg of a spread. A put purchase may hedge a long portfolio. Neither sweep nor block establishes opening status, beneficial owner, portfolio exposure or informed trading. Execution labels alone provide no verified predictive win rate. These labels are research inputs, not investment advice.
A second leg can reverse the apparent size of the bet
Extend the hypothetical example only if reliable linkage identifies another leg: the same participant buys the 600 XYZ $100 calls for $120,650 and sells 600 XYZ $105 calls, with the same expiry, at $0.90 for $54,000. The net debit is $66,650. Adding absolute leg premiums produces $174,650 of gross traded premium; calling that amount a bullish cash outlay would be wrong.
Under the stated opening call-spread assumption, the five-dollar width gives $300,000 maximum expiration value, so maximum expiration profit is $300,000 − $66,650 = $233,350 before fees. These payoff numbers describe the assumed combined position, not a conclusion recoverable from an isolated call print. Unlinked simultaneous trades, closing spreads, rolls with different expirations and stock-option combinations require different treatment.
Inspect multi-leg conditions and source linkage before assigning a strategy. Similar timestamps and matching size are clues, not proof that two prints share an owner. The provider's multi-leg explanation also distinguishes possible strategy identification from certainty.
What Pineify Market Insights actually shows
Sign in and open Market Insights, select Options Flow, then use the ticker, Sweep and premium filters to inspect available alerts. The implementation reviewed on October 18, 2026 requests Unusual Whales flow alerts and displays the upstream sweep flag. It does not independently reconstruct cross-venue parent orders or publish the upstream grouping window. The main row carries alert creation time, total size and total premium; it is not necessarily one execution.
Expand a row for recent contract prints with time, price, size, side and premium. This view currently shows up to 12 returned prints from a contract request of up to 80; it is not restricted to the constituents of that alert. It does not display venue or the quote timestamp, and displayed times omit milliseconds. Those limits prevent the UI alone from verifying the 80-millisecond example above. The data contract has exchange, execution time, NBBO and report-condition fields, but field availability is not proof of a complete synchronized tape.
The sentiment badge is another calculation: calls are labeled bullish when ask-side premium exceeds 60% of total premium, and bearish when bid-side premium exceeds 60%; puts reverse those labels. Exactly 60% does not pass the strict threshold. This measures a premium split, not the trader's intent. The expanded ask/bid mix bar instead divides by ask plus bid premium, so its percentage can differ when total premium includes other classifications.
For example, $55,000 ask-side and $25,000 bid-side out of $100,000 total gives a 68.75% ask share of classified ask/bid premium but only 55% of total. The call remains neutral under the sentiment rule. Use the badge to locate records for inspection. The verified view has no separate Block badge; a large row without Sweep is not automatically a block. Access, caching, provider coverage and record limits affect what is returned, so this guide makes no fixed execution-to-screen latency claim.
FAQ
Frequently Asked Questions