thetaOwl
HomeOptionsORCLReports

ORCL

Oracle CorporationClose $175.07EOD only
Max Pain
$190.00
Next expiry Jun 26, 2026
Expected Move
±$9.25
5.3% from close
Price Gap
+14.93
Distance to max pain
IV Rank
11
Low premium
P/C OI
0.99
Balanced positioning
Consensus
7.0/10
Bullish tilt
Published snapshot: Jun 22, 2026 close
End-of-day snapshot

This page reflects ORCL options positioning from the latest published market-close snapshot. Intraday price and contract changes are not displayed.

Published Snapshot
Jun 22, 2026 close
ORCL AI Consensus Report
Analysis based on market close June 23, 2026
DirectionalTheta GangFlowEarningsConsensus

Historical consensus-supported lens with full content, report chain context, and metric rail.

Conviction
5.5

out of 10

5.5 not 7 because bullish call buying from flow undermines the bearish consensus, and theta's caution limits trade recommendations; higher conviction would require alignment on direction.

Where Perspectives Agree

Cautious bearish bias with high volatility and negative gamma; spot below max pain increases pin risk, and $150 support is critical.

Where They Diverge

Flow shows aggressive call buying at $170-$175 contradicting the bearish directional thesis, while theta advises against new premium selling due to pin risk and high IV, conflicting with directional's bearish put spreads.

Top Trade
via directional

Buy Sep 18 $135/$130 bear put spread for $1.20 debit

Key Risk

Break below $150 invalidates the thesis, triggering dealer short-gamma amplification and downside acceleration toward $140.

How to Use These Reports
This ai consensus reflects the market close on June 23, 2026.
What the reports do

Each report translates the same market-close options snapshot into a specific lens such as directional bias, premium-selling posture, flow quality, or earnings setup.

How traders use them

Reports are most useful for narrowing the playbook, surfacing entry and risk context, and deciding which raw data page to inspect next.

What to remember

These are interpretation layers, not execution guarantees. Validate the setup against chain liquidity, expected move, and exposure before sizing risk.

If the report conviction and the raw data disagree, slow down and resolve the mismatch before sizing risk.