← previous blocknext block →recent activity
Analyzing
Block #98,537,292
13 transactions · 12 stateful · 2026-08-23 17:29:37 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,537,292 · 13 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
1w03w04w16w08w19w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa02838a3…bc54
0x34b655…2a6f
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x48717abe…be13
0x34b655…2a6f
2 touches
0 conflicts
0x5aed1bd2…7afa
0x34b655…2a6f
2 touches
0 conflicts
0x9b36f19f…fa5a
0x34b655…2a6f
2 touches
0 conflicts
0xa03ccaf7…c77f
0x34b655…2a6f
2 touches
0 conflicts
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity