Unusual options activity is trading in a contract far beyond what is normal for it, most often measured as the day's volume divided by its open interest. When a contract trades many times the contracts already open, someone has probably opened a new position. It may also be a big trade that both opened and closed, so you have to look at the trades themselves.
This post finds it in two steps with the free DIS samples from 2026-10-15: screen the option chain file, then read the trade file. Both run in DuckDB.
Step 1: screen the chain by volume over open interest
The chain file has each contract's volume for the day and its oi, the open interest at the previous close. Divide one by the other, and require enough volume to matter:
SELECT expiration_date, strike, put_call, volume, oi,
round(volume / oi, 1) AS vol_oi
FROM 'DIS_chains_2026-10-15.parquet'
WHERE volume >= 500 AND oi > 0
ORDER BY vol_oi DESC
LIMIT 3;| Expiration | Strike | Side | Volume | Open interest | Volume / OI |
|---|---|---|---|---|---|
| 2026-10-16 | 111 | Put | 1,670 | 12 | 139.2 |
| 2026-10-23 | 109 | Put | 2,910 | 72 | 40.4 |
| 2027-09-17 | 95 | Put | 821 | 92 | 8.9 |
Two contracts stand out: the 111 put expiring the next day, at 139 times its open interest, and the next week's 109 put, at 40 times. The volume threshold matters: without it, a contract with 1 open and 10 traded would top the list.
Step 2: read the trades behind them
The trade file has every trade with the bid and ask at that moment, so you can see how each contract traded:
SELECT strike, expiration_date,
count(*) AS trades,
sum(size) AS contracts,
sum(size) FILTER (WHERE price >= ask) AS at_or_above_ask,
sum(size) FILTER (WHERE price <= bid) AS at_or_below_bid,
max(size) AS largest_trade,
round(sum(price * size * 100)) AS premium
FROM 'DIS_2026-10-15.parquet'
WHERE put_call = 'PUT'
AND ((strike = 109 AND expiration_date = DATE '2026-10-23')
OR (strike = 111 AND expiration_date = DATE '2026-10-16'))
GROUP BY strike, expiration_date
ORDER BY strike;| Contract | Trades | Contracts | At or above ask | At or below bid | Largest trade | Premium |
|---|---|---|---|---|---|---|
| 109 put, Oct 23 | 92 | 2,910 | 648 | 2,214 | 880 | $257,338 |
| 111 put, Oct 16 | 88 | 1,670 | 164 | 37 | 600 | $97,390 |
The two look different:
- The 109 put traded mostly at the bid. 2,214 of 2,910 contracts printed at or below the bid, and the two largest trades, 880 and 608 contracts, went through at the same second, 10:48:26 New York time, each at the bid. Trades at the bid usually mean a seller crossed the spread, so this leans toward puts being sold.
- The 111 put traded mostly between the bid and ask. Only 201 of 1,670 contracts printed at either side. Its largest trades, 600 and 400 contracts, went through together at 14:05:39 at 0.51, the midpoint of a 0.45 to 0.57 market. Midpoint prints say little about direction on their own.
The volumes add up: the trade file's 2,910 and 1,670 contracts are exactly the chain file's volume.
Step 3: check the next day's open interest
Volume can't tell you whether a trade opened or closed a position. The next day's chain answers it: if open interest rose by about the volume, new positions were opened. Buy two consecutive chain days and compare oi for the same contract. Open interest in each file is as of the previous close, so the 2026-10-16 file shows the result of 2026-10-15's trading.
What to keep in mind
- A high ratio on a tiny open interest is common in contracts that just listed or have been quiet.
- Trading at the bid or ask suggests who started a trade, not why. A put sold may be a hedge, an income trade, or the other side of a spread.
- One day is an anecdote. The pattern is worth more when you screen many days the same way.
Option chain files cost $1 a day for the whole market, with a $2 minimum. Option trade files cost $2 a day for the whole market, or $1 per 10 million rows for chosen symbols. For more on loading the trade file, see querying trade files with DuckDB.
Frequently asked questions
What volume-to-open-interest ratio counts as unusual? There is no fixed cutoff. Many screens start at about 2 to 5 times, with a minimum volume; rank by the ratio and read the top contracts.
Why use the chain file for the screen and not the trade file? The chain file already has each contract's daily volume next to its open interest, one row per contract, so the screen is one fast query across the whole market.
Does the chain's volume include every trade? It counts every session ThetaData's end-of-day report counts. For SPX, SPXW, XSP and VIX that includes overnight trading.