← previous blocknext block →recent activity
Analyzing
Block #86,928,779
14 transactions · 11 stateful · 2026-07-10 22:31:44 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,928,779 · 14 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
6w07w08w19w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6dcb5d8d…5f07
0x34b655…2a6f
6 touches
3 conflicts
0xc9cbb059…9e23
0x34b655…2a6f
6 touches
3 conflicts
0x173337fe…f0af
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x552ac70a…d74b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
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
3 conflicts on slot 0x6dcb5d8d44…cd5f07
Audit this contract →
← previous block·next block →recent activity