← previous blocknext block →recent activity
Analyzing
Block #86,677,624
13 transactions · 11 stateful · 2026-07-09 18:33:25 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,677,624 · 13 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
1w03w04w15w28w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ea2b1f6…1d57
0x34b655…2a6f
4 touches
1 conflict
0x1ea2b1f6…1d58
0x34b655…2a6f
4 touches
1 conflict
0x20492d53…80f9
0x34b655…2a6f
4 touches
1 conflict
0x259f3ba0…a139
0x34b655…2a6f
4 touches
1 conflict
0x33b0c9bc…ad72
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
4 touches
1 conflict
0x6a83b716…00cc
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0x1ea2b1f6f8…631d57
Audit this contract →
← previous block·next block →recent activity