← previous blocknext block →recent activity
Analyzing
Block #96,603,611
45 transactions · 43 stateful · 2026-08-16 22:01:02 UTC
Parallelism
71/100
Blocked
79%
Avg conflicts / tx
2.53
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #96,603,611 · 45 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w15w26w37w08w19w110w212w213w314w415w517w618w719w826w729w833w236w438w541w944w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
18 touches
36 conflicts
0xb9834665…e363
0x34b655…2a6f
14 touches
21 conflicts
0xb13b96bd…a3cb
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x7de57974…f5ba
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 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
36 conflicts on slot 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity