← previous blocknext block →recent activity
Analyzing
Block #85,126,070
58 transactions · 47 stateful · 2026-07-02 14:01:53 UTC
Parallelism
64/100
Blocked
72%
Avg conflicts / tx
3.29
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #85,126,070 · 58 txs across 21 waves · depth 21
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
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w18w29w211w312w415w516w217w622w123w749w750w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
32 touches
120 conflicts
0xf6900791…657f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
16 touches
28 conflicts
0x3230277c…ef39
0xc8689a…ee79
16 touches
28 conflicts
0xcffc17bc…3544
0x34b655…2a6f
14 touches
21 conflicts
0x0934ec4c…50c8
0x34b655…2a6f
14 touches
21 conflicts
0xd92a03c7…bfc7
0x34b655…2a6f
14 touches
21 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
120 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity