← previous blocknext block →recent activity
Analyzing
Block #86,657,708
16 transactions · 12 stateful · 2026-07-09 16:20:33 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.31
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,657,708 · 16 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
2w03w15w06w17w28w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x37ee30c9…9e70
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x64a785e4…0110
0x34b655…2a6f
4 touches
1 conflict
0x680ca7d7…2df4
0x34b655…2a6f
4 touches
1 conflict
0x7048d42f…288b
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
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
15 conflicts on slot 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity