← previous blocknext block →recent activity
Analyzing
Block #86,817,944
10 transactions · 9 stateful · 2026-07-10 10:10:36 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,817,944 · 10 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
3w04w16w27w38w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e8ebc95…aded
0x34b655…2a6f
6 touches
3 conflicts
0x1b8a7196…df2d
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x2375f8f8…2468
0x34b655…2a6f
4 touches
1 conflict
0x3483ab79…8ed3
0x34b655…2a6f
4 touches
1 conflict
0x4aca1888…420c
0x34b655…2a6f
4 touches
1 conflict
0x52836aee…096e
0x34b655…2a6f
4 touches
1 conflict
0x5c4300a8…c840
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 0x7e8ebc95eb…49aded
Audit this contract →
← previous block·next block →recent activity