← previous blocknext block →recent activity
Analyzing
Block #85,101,969
21 transactions · 20 stateful · 2026-07-02 11:20:23 UTC
Parallelism
57/100
Blocked
45%
Avg conflicts / tx
1.67
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #85,101,969 · 21 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w610w719w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1647db7…f853
0x34b655…2a6f
16 touches
28 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0xffb8950c…23c6
0x34b655…2a6f
16 touches
28 conflicts
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x922c7ebd…6600
0xc8689a…ee79
16 touches
28 conflicts
0x7e75ae59…33fc
0x34b655…2a6f
16 touches
28 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
16 touches
28 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
28 conflicts on slot 0xc1647db712…42f853
Audit this contract →
← previous block·next block →recent activity