← previous blocknext block →recent activity
Analyzing
Block #85,810,679
12 transactions · 9 stateful · 2026-07-05 18:02:29 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,810,679 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc10b903d…2f54
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0x6e19b081…7cec
0x34b655…2a6f
4 touches
1 conflict
0x08de772c…8e84
0x2a68ba…90c5
2 touches
0 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
2 touches
0 conflicts
0x0d6d262c…958d
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x9a3068dd…18f0
0x34b655…2a6f
2 touches
0 conflicts
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 0xc10b903def…412f54
Audit this contract →
← previous block·next block →recent activity