← previous blocknext block →recent activity
Analyzing
Block #91,416,960
37 transactions · 33 stateful · 2026-07-29 18:36:58 UTC
Parallelism
70/100
Blocked
64%
Avg conflicts / tx
1.51
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #91,416,960 · 37 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w06w211w112w213w314w016w118w019w120w221w323w424w525w626w127w228w631w132w833w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4e0a934…5fc7
0x34b655…2a6f
10 touches
10 conflicts
0xfbe6a366…8ca1
0x34b655…2a6f
10 touches
10 conflicts
0xfb874a6c…caa0
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xd8e710e7…d5b7
0xd32edf…ff58
7 touches
6 conflicts
0x7604a8f8…d63a
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
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
10 conflicts on slot 0xb4e0a934b9…435fc7
Audit this contract →
← previous block·next block →recent activity