← previous blocknext block →recent activity
Analyzing
Block #86,565,413
25 transactions · 24 stateful · 2026-07-09 06:01:28 UTC
Parallelism
76/100
Blocked
46%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,565,413 · 25 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
1w02w16w07w18w29w310w411w514w115w220w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bfc029c…f91e
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x727fbce7…0c80
0x34b655…2a6f
6 touches
3 conflicts
0xa1571d54…ae41
0x34b655…2a6f
6 touches
3 conflicts
0xc368d7fd…aaec
0x34b655…2a6f
6 touches
3 conflicts
0x2a7c9c41…65ec
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
10 conflicts on slot 0x1bfc029c66…d5f91e
Audit this contract →
← previous block·next block →recent activity