← previous blocknext block →recent activity
Analyzing
Block #91,111,479
14 transactions · 13 stateful · 2026-07-28 16:58:47 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,111,479 · 14 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
3w07w111w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6aea3f64…bb1f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1c0ef569…adf7
0x34b655…2a6f
4 touches
1 conflict
0x42cbd3f5…5c0b
0x34b655…2a6f
4 touches
1 conflict
0x4ca5fbf0…6059
0x34b655…2a6f
4 touches
1 conflict
0x600ca1f7…b772
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0x6aea3f6436…44bb1f
Audit this contract →
← previous block·next block →recent activity