← previous blocknext block →recent activity
Analyzing
Block #85,928,979
18 transactions · 16 stateful · 2026-07-06 07:10:25 UTC
Parallelism
78/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,928,979 · 18 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
1w06w07w08w19w110w011w012w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d6c45c2…eea2
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xef8649cd…8ebc
0x34b655…2a6f
5 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5bb2ef40…3b0b
0x34b655…2a6f
4 touches
1 conflict
0x64df3bfd…6dd4
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0x7e17e82a…9748
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 0x0d6c45c229…bceea2
Audit this contract →
← previous block·next block →recent activity