TOTAL VOLUME:

$134.2b

24H VOL:

$134,145,987

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,441,166,947

406,422

Markets across

30,383

events

MATCHED EVENTS:

2,688

PLATFORM COVERAGE:

5

Polymarket:

39%

VS.

Kalshi:

61%

BETA
Dashboards
Insights
Indices
Tour
All
Trending
Breaking
New
Ending Soon
Politics
Sports
Crypto
Companies
Elections
Financials
Economics
Other
Entertainment
Science and Technology
Arizona vs San Diego: 2nd Inning Winner
kalshi

Arizona vs San Diego: 2nd Inning Winner

Volume:
$74

Arizona wins 2nd inning

 - Kalshi

Arizona wins 2nd inning - Kalshi

1W

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Sep 27, 2026

Closed: Sep 26, 9:35 PM EST

kalshi

Kalshi

View
Join Kalshi and score $25 for your first trade.
Outcome
Trade
Chance %
Price
Spread
Liquidity
Volume
24h
7d
Open Interest
Ends in
Result
kalshi

Arizona wins 2nd inning

View
100%
Yes 100¢No 0¢
100¢
N/A
$43
N/A
N/A
$43
Settled
Yes
kalshi

San Diego wins 2nd inning

View
0%
Yes 0¢No 100¢
100¢
N/A
$31
N/A
N/A
$30
Settled
No
kalshi

Tie 2nd inning

View
N/A
N/A
100¢
N/A
N/A
N/A
N/A
N/A
Settled
No
Total markets: 3

Description

This market focuses on determining which team will score more runs in a specific inning of an upcoming baseball game. It highlights the competitive nature of early-game performance between two teams. The outcome depends solely on the runs scored during that inning, regardless of the final game result.

Kalshi

If Arizona scores more runs in the 2nd inning of the Arizona vs San Diego professional baseball game originally scheduled for Sep 26, 2026 at 8:40 PM EDT, then the market resolves to Yes. If San Diego scores more runs in the 2nd inning of the Arizona vs San Diego professional baseball game originally scheduled for Sep 26, 2026 at 8:40 PM EDT, then the market resolves to Yes. If neither Arizona nor San Diego scores more runs in the 2nd inning of the Arizona vs San Diego professional baseball game originally scheduled for Sep 26, 2026 at 8:40 PM EDT, then the market resolves to Yes.