← previous blocknext block →recent activity
Analyzing
Block #86,660,183
25 transactions · 19 stateful · 2026-07-09 16:37:04 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,660,183 · 25 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
4w05w16w07w19w010w011w115w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe6805ef8…e22e
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8388eab6…83ff
0x34b655…2a6f
4 touches
1 conflict
0x9021aa0c…20ac
0x34b655…2a6f
4 touches
1 conflict
0x9c449f77…6992
0x34b655…2a6f
4 touches
1 conflict
0x9e9c4e1e…4f14
0x34b655…2a6f
4 touches
1 conflict
0xa7707869…e2f6
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity