← previous blocknext block →recent activity
Analyzing
Block #86,491,257
21 transactions · 18 stateful · 2026-07-08 21:45:27 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,491,257 · 21 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
3w06w07w19w010w112w214w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfefb0189…f726
0x34b655…2a6f
8 touches
6 conflicts
0xa584fb3d…c78d
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5e782d17…5317
0x34b655…2a6f
6 touches
3 conflicts
0xda8d6085…7b09
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x080ec687…da80
0x34b655…2a6f
6 touches
3 conflicts
0x418a7b19…b8ca
0x34b655…2a6f
5 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 0xfefb01895a…9bf726
Audit this contract →
← previous block·next block →recent activity