← previous blocknext block →recent activity
Analyzing
Block #91,096,308
41 transactions · 36 stateful · 2026-07-28 15:42:27 UTC
Parallelism
66/100
Blocked
67%
Avg conflicts / tx
3.07
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #91,096,308 · 41 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w07w18w210w011w112w013w114w115w217w218w320w121w323w424w525w626w727w828w929w1030w1131w1232w1335w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
28 touches
91 conflicts
0x482471ad…122f
0x34b655…2a6f
26 touches
78 conflicts
0xbde524f4…43bf
0x34b655…2a6f
22 touches
55 conflicts
0x705ab4ae…0162
0x34b655…2a6f
20 touches
45 conflicts
0xb726505b…f6bd
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
8 touches
6 conflicts
0x23df630a…22a5
0x34b655…2a6f
7 touches
6 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
91 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity