← previous blocknext block →recent activity
Analyzing
Block #86,775,067
12 transactions · 11 stateful · 2026-07-10 05:24:15 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,775,067 · 12 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
2w04w05w16w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ef38617…f0f2
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x469dac8d…3411
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x58693d48…0f7c
0x34b655…2a6f
4 touches
1 conflict
0x6122676a…1970
0x34b655…2a6f
4 touches
1 conflict
0x6122676a…1971
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
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 0x9ef386173a…d2f0f2
Audit this contract →
← previous block·next block →recent activity