← previous blocknext block →recent activity
Analyzing
Block #99,037,807
12 transactions · 12 stateful · 2026-08-25 11:59:53 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,037,807 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w27w310w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf3981be5…2c47
0x34b655…2a6f
4 touches
1 conflict
0x10d80fee…dbda
0x2b46c0…1669
2 touches
0 conflicts
0x40970e69…da50
0x2b46c0…1669
2 touches
0 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
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