← previous blocknext block →recent activity
Analyzing
Block #86,319,385
22 transactions · 19 stateful · 2026-07-08 02:36:54 UTC
Parallelism
82/100
Blocked
26%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,319,385 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w110w011w112w217w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c04ce68…d007
0x34b655…2a6f
8 touches
6 conflicts
0x4abfb389…18f4
0x34b655…2a6f
6 touches
3 conflicts
0x5e782d17…5317
0x34b655…2a6f
6 touches
3 conflicts
0x5e782d17…5318
0x34b655…2a6f
6 touches
3 conflicts
0xc6f4f168…765c
0x34b655…2a6f
6 touches
3 conflicts
0xa6673953…467d
0x34b655…2a6f
4 touches
2 conflicts
0x9365e097…ff56
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
6 conflicts on slot 0x4c04ce6804…bbd007
Audit this contract →
← previous block·next block →recent activity