← previous blocknext block →recent activity
Analyzing
Block #89,404,379
24 transactions · 23 stateful · 2026-07-22 10:29:18 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,404,379 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w08w110w012w013w114w215w216w219w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4681609f…6493
0x34b655…2a6f
8 touches
6 conflicts
0x4706a7f7…6937
0x0a2fbf…29b1
6 touches
3 conflicts
0x4706a7f7…6938
0x0a2fbf…29b1
6 touches
3 conflicts
0xb69ee5a5…b82b
0x0a2fbf…29b1
6 touches
3 conflicts
0xb69ee5a5…b82c
0x0a2fbf…29b1
6 touches
3 conflicts
0xb69ee5a5…b82f
0x0a2fbf…29b1
6 touches
3 conflicts
0x55b4e430…44cb
0x754704…b603
6 touches
3 conflicts
0x6fe7d366…78ff
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
6 conflicts on slot 0x4681609fd4…e96493
Audit this contract →
← previous block·next block →recent activity