Bitcoin and Ethereum implied volatility today

Current source-backed snapshot

This page compares Deribit's current BTC and ETH DVOL readings with their 24-hour change and seven-day range, then places them beside annualized realized volatility from closed Binance USDT hourly returns. Implied volatility reflects option-market pricing; realized volatility describes movement that already occurred. Their gap can show volatility repricing, but it does not forecast an exact price range or say that options are cheap or expensive for a specific strategy.

Input documentation: Deribit volatility index · Binance Spot klines

Observation window: Current, 24-hour and seven-day DVOL context with 7-day and 30-day annualized realized volatility

Calculation cadence: Auto-refresh about every 900 seconds

Calculation version: iv-rv-1.1

Download current dataset: JSON · CSV Raw values retain the dataset's published precision. Free fair-use limit: 60 requests per minute per IP, shared across all Research JSON and CSV endpoints.

Current source health

• deribit volatility: live; last success 2026-09-13 15:35:24 UTC
• research long candles: live; last success 2026-09-13 15:35:35 UTC

DVOL is a Deribit option-market index, not a forecast of exact price range. Realized volatility uses Binance USDT hourly returns; IV minus RV is a context comparison, not an options valuation or trade recommendation.

How to read this page

• DVOL is annualized volatility points, not expected return.
• The 24-hour change is points, not percent.
• Realized volatility uses closed hourly log returns.
• A positive IV–RV gap is not guaranteed option richness.

What can this page tell you quickly?

Best for

Seeing whether options volatility repriced versus spot movement.

Coverage

BTC and ETH DVOL plus Binance realized volatility.

Windows

Current, 24 hours, seven days and 30-day context.

Do not infer

DVOL does not predict exact range or option profit.

What is the difference between implied and realized volatility?

Implied volatility comes from option prices and reflects option-market uncertainty across strikes and maturities. Realized volatility comes from past returns and therefore looks backward.

They differ because traders pay for protection or convexity and sellers require compensation. A gap is a condition to investigate, not proof of mispricing.

How should a 24-hour DVOL change be read?

A move from 40 to 45 is five points, not a 5% asset-price prediction. Price can be flat while IV rises before an event, or move sharply while IV falls if uncertainty was already priced.

The seven-day range shows whether today's reading is near a recent extreme but cannot reveal the exact strike, expiry or skew driving the index.

How does CoinNudge calculate realized volatility?

For every closed hour, CoinNudge calculates the natural logarithm of current close divided by prior close. The population standard deviation is multiplied by the square root of 8,760 and shown as annualized percent.

Seven-day RV needs 169 closes and 30-day RV needs 721. Incomplete baselines remain blank rather than becoming zero.

What can an aggregate volatility index leave out?

DVOL condenses information from a range of Deribit options into one index level. A single value cannot show whether short-dated options are pricing a near event more aggressively than longer maturities, whether downside puts carry a larger premium than upside calls, or which strike contributed most to the change. Those questions require term-structure and skew data beyond this page.

The distinction matters around scheduled catalysts. DVOL may rise while spot remains quiet because option participants are paying for uncertainty before an event. After the event, DVOL can fall even if spot moves sharply because the unresolved risk has passed. Neither sequence makes the index a directional signal.

BTC and ETH can also show different gaps because their option liquidity, realized paths and event exposures differ. CoinNudge therefore presents each asset separately and never averages them into a market-wide fear score.

Use the current level, 24-hour point change, seven-day range and realized-volatility comparison as an investigation order. Before evaluating an option position, separately inspect maturity, strike, skew, bid-ask spread, transaction costs and the loss profile of the actual strategy.

When is a volatility alert useful?

A useful alert identifies whether DVOL moved, reached a recent extreme or diverged from realized volatility, and states the unit and window. Direction is separate because volatility expands both upward and downward.

Telegram delivery should suppress tiny changes and repeated states. The message is an attention and risk signal, not an option trade recommendation.

The first useful follow-up is to compare the alert timestamp with the spot move and any known event calendar. Rising DVOL with quiet spot can indicate that uncertainty is being repriced before price reacts; rising DVOL after a large spot move may instead reflect demand for protection after the move. The same index change therefore needs different interpretation in different sequences.

An alert should also preserve the baseline behind the comparison. CoinNudge reports the current index level, the change in volatility points, the recent range and realized-volatility windows together so a reader can distinguish a fresh repricing from a value that was already elevated. Missing 7-day or 30-day history remains unavailable rather than being displayed as zero.

This page does not compare option premiums, break-even prices or strategy Greeks. Before acting on any volatility observation, inspect the actual expiry and strike, bid-ask spread, implied-volatility skew, event timing and maximum loss of the position being considered.

Can the difference between implied and realized volatility be treated as an option-selling return?

No. It compares an option-implied measure with a backward-looking realized measure. An actual option outcome also depends on the contract, execution, path, hedging and costs.

An IV-minus-RV spread is research context rather than an executable premium or promised yield. Options history requires its own coverage review.

• Check the DVOL horizon and the return interval used to calculate realized volatility.
• Keep annualization and units consistent before subtracting values.
• Save observation times and analyze later realized paths separately from the original implied reading.

Verify: Deribit volatility index · Binance Spot klines

What is measured, and what is not?

Method and data boundary

CoinNudge requests hourly Deribit volatility-index candles for the latest eight days. Current DVOL is compared with the closest observation 24 hours earlier and the seven-day high and low. Seven-day and 30-day realized volatility use the population standard deviation of hourly log returns from closed Binance BTCUSDT and ETHUSDT candles, annualized by the square root of 365 times 24.

DVOL is a Deribit option-market index, while realized volatility uses Binance USDT spot. Different venues, instruments, sampling and option maturities make the values contextually comparable but not interchangeable valuations.

Read the complete CoinNudge methodology

Sources and verification

• Deribit volatility indexHourly BTC and ETH DVOL OHLC.
• Binance Spot klinesClosed hourly spot prices for RV.

Frequently asked questions

Receive explained volatility changes in Telegram

Know whether the options market repriced and how that compares with realized movement.