| Outcome | Probability | Yes Bid | Yes Ask | 24h Change | Volume | |
|---|---|---|---|---|---|---|
| Target Price: $646.82 | 0% | 0¢ | 0¢ | — | $0 | Trade → |
This market asks whether Binance Coin (BNB) will hit a price target of $646.82 within a single 15-minute interval as defined by the platform. It matters because short-window price targets let traders express views on immediate volatility and liquidity around a specific price level.
BNB is the native token of the Binance ecosystem and is sensitive to exchange flows, Binance-related announcements, and broad crypto market moves. Fifteen-minute targets capture high-frequency drivers—order‑book imbalances, large market orders, liquidations, and news shocks—that can produce rapid price swings, so these markets tend to be more reactive than longer-term forecasts.
Market odds aggregate participants' views and available information about whether the target will be reached during any qualifying 15-minute window; treat them as a dynamic consensus signal rather than a definitive prediction.
The platform uses the timestamping rules and reference feed specified in the event's settlement terms to identify qualifying 15-minute windows; check the event rules on KALSHI to see whether windows can start at any second or are aligned to fixed clock intervals.
Settlement is determined by the price feed or composite data source named in the event's rules on KALSHI (for example, a specific exchange trade price or an aggregate); consult the event details to see the designated source.
The event wording and settlement rules specify whether an exact match counts or whether the price must exceed the target; review the event's precise language to know which condition applies.
That figure reports activity on the prediction market itself and does not influence the underlying price determination; settlement is based on the external reference price feed, not on on-platform trading volume.
KALSHI's abnormal-data and dispute procedures apply: they may use alternate feeds, delay settlement, or follow backup rules defined in the event documentation—check the event's rulebook or help center for the precise contingency steps.