← previous blocknext block →recent activity
Analyzing
Block #86,665,299
18 transactions · 18 stateful · 2026-07-09 17:11:10 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,665,299 · 18 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
3w04w15w26w37w08w19w213w416w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3e06ffb…6c2b
0x34b655…2a6f
10 touches
10 conflicts
0x1951ee47…540f
0x34b655…2a6f
8 touches
6 conflicts
0x0e9a70ab…e67c
0x34b655…2a6f
8 touches
6 conflicts
0x3d4584df…ffed
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x548145a9…cfce
0x34b655…2a6f
8 touches
6 conflicts
0x727fbce7…0c80
0x34b655…2a6f
8 touches
6 conflicts
0x9ad66bbf…929c
0x34b655…2a6f
8 touches
6 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 0xa3e06ffb4c…916c2b
Audit this contract →
← previous block·next block →recent activity