TOTAL VOLUME:

$134.2b

24H VOL:

$130,522,377

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,438,389,636

404,028

Markets across

30,214

events

MATCHED EVENTS:

2,681

PLATFORM COVERAGE:

5

Polymarket:

39%

VS.

Kalshi:

61%

BETA
Dashboards
Tour
All
Sports
Counter-Strike: MOUZ NXT vs UNiTY esports (BO3) - European Pro League Series 5 Playoffs
kalshi
polymarket

Counter-Strike: MOUZ NXT vs UNiTY esports (BO3) - European Pro League Series 5 Playoffs

Volume:
$25,502

MOUZ NXT

all

2 markets

Kalshi

Polymarket

consensus

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Mar 15, 2026

Closed: Mar 6, 8:00 AM 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

MOUZ NXT

View
100%
Yes 100¢No 0¢
—
N/A
$14,367
N/A
N/A
$11,895
Settled
Yes
polymarket

Match Winner

N/A
N/A
—
N/A
N/A
N/A
N/A
N/A
Settled
Yes
polymarket

Odd/Even Total Kills

100%
Yes 100¢No 0¢
—
N/A
$99
N/A
N/A
N/A
Settled
Yes
kalshi

UNiTY esports

0%
Yes 0¢No 100¢
—
N/A
$10,929
N/A
N/A
$9,749
Settled
No
polymarket

Odd/Even Total Kills

0%
Yes 0¢No 100¢
—
N/A
$107
N/A
N/A
N/A
Settled
No
polymarket

Map 1 Winner

N/A
N/A
—
N/A
N/A
N/A
N/A
N/A
Settled
Yes
polymarket

Map 2 Winner

N/A
N/A
—
N/A
N/A
N/A
N/A
N/A
Settled
Yes
polymarket

O/U 2.5 Games

N/A
N/A
—
N/A
N/A
N/A
N/A
N/A
Settled
No
polymarket

Map Handicap: MOUZ.N (-1.5) vs UNiTY esports (+1.5)

N/A
N/A
—
N/A
N/A
N/A
N/A
N/A
Settled
Yes
polymarket

Odd/Even Total Rounds

N/A
N/A
—
N/A
N/A
N/A
N/A
N/A
Settled
No
polymarket

Odd/Even Total Kills

N/A
N/A
—
N/A
N/A
N/A
N/A
N/A
Settled
No
polymarket

Odd/Even Total Rounds

N/A
N/A
—
N/A
N/A
N/A
N/A
N/A
Settled
No
polymarket

Odd/Even Total Rounds

N/A
N/A
—
N/A
N/A
N/A
N/A
N/A
Settled
Yes
Total markets: 13

Description

This event group covers a Counter-Strike Best-of-3 match between MOUZ NXT and UNiTY esports in the European Pro League Series 5 Playoffs, scheduled for March 6, 2026 at 4:00 AM ET. Markets span match outcome, individual map winners, map counts, handicaps, and granular kill/round parity across all three maps.

PredictionHero - Resolution Divergence Alerts (RDA)

Divergence Detected

Issue: Kalshi defines resolution at the tournament level (EPL S5 winner), while Polymarket defines all markets at the match level (Round of 16 BO3 on March 6). This is a scope mismatch that makes cross-platform settlement impossible and creates two entirely separate resolution universes.Hero tip: Do not assume Kalshi and Polymarket markets are fungible. Kalshi resolves YES if either team wins the entire EPL S5 tournament; Polymarket markets resolve based solely on the March 6 BO3 match result. A team can win the match but lose the tournament (or vice versa). Treat these as independent contracts.

Critical divergence points:

  • Kalshi: Tournament-level resolution. Market resolves YES if UNiTY esports OR MOUZ NXT wins the European Pro League Series 5 2026 tournament. Quote: 'If UNiTY esports wins the European Pro League Series 5 2026: UNiTY esports vs. MOUZ NXT CS2 match originally scheduled for Mar 6, 2026, then the market resolves to Yes.' This is ambiguous and conflates match participation with tournament victory.
  • Polymarket: Match-level resolution. All 10 markets (Match Winner, Map 1/2/3 Winners, Games Total, Handicap, Odd/Even Kills/Rounds per map) resolve exclusively on the BO3 match outcome on March 6. Quote: 'This market refers to the Counter-Strike Round of 16 match between MOUZ NXT and UNiTY esports in the European Pro League Series 5 Playoffs, initially scheduled for March 6 at 4:00AM ET.' Clear, match-specific scope.
Our PredictionHero Resolution Divergence Alerts (RDA) are there to help users identify potential differences across platforms. They do not replace or supersede the official rules and description of any prediction market. Users are solely responsible for reviewing and understanding the applicable rules and resolution criteria before placing any trade or bet. If you notice a potential inconsistency, discrepancy, or error in an alert, please report it to our team so we can review and improve the accuracy of our data.