← previous blocknext block →recent activity
Analyzing
Block #86,693,418
12 transactions · 8 stateful · 2026-07-09 20:18:49 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,693,418 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bfc029c…f91e
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x45b4ce01…6caa
0x34b655…2a6f
6 touches
3 conflicts
0x63b15849…80b2
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
6 touches
3 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
6 touches
3 conflicts
0xc435a04a…e025
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
3 conflicts on slot 0x1bfc029c66…d5f91e
Audit this contract →
← previous block·next block →recent activity