Magic vs. Pistons
Probability
38¢
1h
+0.0pp
24h
-0.5pp
24h Vol
$40.02
Liquidity
$10.5K
Probability (last 7 days)
+0.0pp 7dWhy did it move?
Structured · 2 factors- 1
Resolution-risk signal firing
Expires in 85h with open resolution ambiguity.
- 2
Wide spread — 9.0¢
Bid-ask spread is wide enough that intraday moves overstate any tradeable edge. Most of the headline pp move would be eaten by spread on a market order.
What to track next
- Verify the resolution source on this page — exchange feed, official release, news consensus — before treating any move as new information.
Verification actions only — never trade recommendations.
Each factor is grounded in a single named metric you can verify on this page — probability, volume, liquidity, signal, resolution state. No predictions, no prose hallucinations.
AI prose summary
Prose narration of the same metrics shown in the structured breakdown above. Cites only the market data on this page — no news, no predictions. Use the structured factors as the canonical answer; this is here for readability.
Timeline — news, trades, signals, price moves
- 0s agoResolveLOW
Market resolves in 85.4h
- 14:36SignalLOW
Signal · Resolution risk
Expires in 85h with open resolution ambiguity.
Active signals
Recent Trades
No recent trades visible from the Data API for this market.
Related Markets
3Market Description
In the upcoming NBA game, scheduled for April 29 at 12:00AM ET: If the Magic win, the market will resolve to "Magic". If the Pistons win, the market will resolve to "Pistons". If the game is postponed, this market will remain open until the game has been completed. If the game is canceled entirely, with no make-up game, this market will resolve 50-50. The result will be determined based on the final score including any overtime periods.
Resolution & Risk
LOW risk- End date
- Apr 29, 2026
- UMA status
- n/a
- Resolution source
- https://www.nba.com/
- Market type
- Binary
- Wide spread (9.0¢) — liquidity risk on entry/exit.
Alerts
In-app banners work now. Email / Telegram / Discord delivery lands when the backend alert dispatcher ships (needs RESEND_API_KEY + per-user webhook storage).