← previous blocknext block →recent activity
Analyzing
Block #86,659,585
28 transactions · 17 stateful · 2026-07-09 16:33:05 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.32
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,659,585 · 28 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
1w03w04w15w18w210w113w314w026w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0354962d…a50d
0x34b655…2a6f
4 touches
1 conflict
0x0c84f2dd…068d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2d7ea048…d78e
0x34b655…2a6f
4 touches
1 conflict
0x3a2a8323…3f40
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x67eb9f2d…885a
0x34b655…2a6f
4 touches
1 conflict
0x70df5d25…3fd5
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
1 conflict on slot 0x0354962d81…e0a50d
Audit this contract →
← previous block·next block →recent activity