← previous blocknext block →recent activity
Analyzing
Block #98,741,800
20 transactions · 16 stateful · 2026-08-24 11:07:17 UTC
Parallelism
85/100
Blocked
31%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,741,800 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w07w18w210w113w016w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28470e85…59cc
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xa7b10557…444d
0x34b655…2a6f
4 touches
1 conflict
0xb20094ed…0fef
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x28470e8527…ab59cc
Audit this contract →
← previous block·next block →recent activity