← previous blocknext block →recent activity
Analyzing
Block #89,516,670
17 transactions · 14 stateful · 2026-07-22 22:59:35 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,516,670 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w09w110w211w112w313w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ee3825f…ab52
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xd4230a60…bd13
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x6474161a…6a37
0x34b655…2a6f
4 touches
1 conflict
0x8ad18e06…472a
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
6 conflicts on slot 0x3ee3825f99…a2ab52
Audit this contract →
← previous block·next block →recent activity