What you can do here
The chain combines a CALLS | STRIKE | PUTS layout with OI-by-strike visualisation and ATM/wall/max-pain context. The section=chain route sets the full window, but a saved screenshot can still show a stale ATM badge. Check resolved identity and actual rows, not just header selections, before interpreting a historical capture. The ±5, ±10 and ±20 chips are total strike counts, not per-side counts: ±10 renders 10 strikes in all, roughly five above and five below ATM. Full chain renders every returned strike.
- Compare both option sides at the same strike and expiry.
- Use ±5, ±10, ±20 or Full chain to control the visible ladder.
A look inside Option Chain
From numbers to understanding
- 01
Call and put columns must be compared on the same stored session and expiry.
- 02
OI and OI change are distinct from volume/contracts and option price.
- 03
ATM, maximum OI and max pain highlight different concepts.
- 04
A strike click locates that strike; use the appropriate side's contract link for exact CE/PE identity.
- 05
A ± chip is a total window: ±10 shows about five strikes on each side of ATM.
CAPTURED STRIKE STRUCTURE
Terminal-displayed exampleThe 10 Nov 2026 capture, labelled 9 Nov, displayed underlying reference 25,044.65, 147 strikes, ATM 25,050, call wall 26,000, put wall and max pain 25,000. These are unverified terminal calculations, not authenticated exchange truth. The reference 25,044.65 is not an option premium.
Try it, one step at a time
Use these checkboxes as a reading checklist. They do not perform actions in Prime.
What this does not tell you
Confirm the actual underlying and expiry after loading; stale labels or incomplete imports can make a visually plausible chain misleading.
Analysis, not advice. Past performance does not predict future results. Examples are illustrative; prices, scores and counts may have changed.
Read the full disclaimer ↓