← previous blocknext block →recent activity
Analyzing
Block #91,409,793
35 transactions · 27 stateful · 2026-07-29 18:00:52 UTC
Parallelism
80/100
Blocked
52%
Avg conflicts / tx
0.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,409,793 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w010w112w214w016w117w220w322w023w124w225w327w428w532w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x6c0f3b3c…de17
0xd32edf…ff58
7 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x5a409e7f…09b6
0x2b46c0…1669
6 touches
3 conflicts
0x7a12283f…b18a
0x2b46c0…1669
6 touches
3 conflicts
0x915c095e…c1e5
0x2b46c0…1669
6 touches
3 conflicts
0xcfe06a18…b5b5
0x2b46c0…1669
6 touches
3 conflicts
0xd8fd2add…50fc
0x2b46c0…1669
6 touches
3 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: Perpl
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity