← previous blocknext block →recent activity
Analyzing
Block #89,686,302
11 transactions · 11 stateful · 2026-07-23 17:05:12 UTC
Parallelism
45/100
Blocked
64%
Avg conflicts / tx
1.36
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,686,302 · 11 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
1w02w03w14w25w16w37w48w110w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb9f51f4…0f16
0x34b655…2a6f
8 touches
6 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x7a2c83a3…a29a
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9e70dadd…810d
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 0xfb9f51f42d…620f16
Audit this contract →
← previous block·next block →recent activity