← previous blocknext block →recent activity
Analyzing
Block #86,915,711
17 transactions · 14 stateful · 2026-07-10 21:04:25 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,915,711 · 17 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
3w04w15w28w09w110w211w314w015w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa42e8482…b88f
0x34b655…2a6f
8 touches
6 conflicts
0x99786b6f…44e9
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x02c4bb0f…f2c8
0x34b655…2a6f
8 touches
6 conflicts
0x2d12e250…0970
0x34b655…2a6f
6 touches
3 conflicts
0x405861f3…97d0
0x34b655…2a6f
6 touches
3 conflicts
0x5d7f309d…5145
0x34b655…2a6f
6 touches
3 conflicts
0x7ee6007b…fd68
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 0xa42e848215…53b88f
Audit this contract →
← previous block·next block →recent activity