← previous blocknext block →recent activity
Analyzing
Block #85,100,612
52 transactions · 45 stateful · 2026-07-02 11:11:19 UTC
Parallelism
62/100
Blocked
80%
Avg conflicts / tx
4.77
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #85,100,612 · 52 txs across 20 waves · depth 20
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w310w411w513w614w743w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
40 touches
190 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
20 touches
45 conflicts
0x922c7ebd…6600
0xc8689a…ee79
18 touches
36 conflicts
0xffb8950c…23c6
0x34b655…2a6f
18 touches
36 conflicts
0xc1647db7…f853
0x34b655…2a6f
18 touches
36 conflicts
0xe47478a3…a058
0x34b655…2a6f
18 touches
36 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
18 touches
36 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
18 touches
36 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
190 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity