← previous blocknext block →recent activity
Analyzing
Block #85,128,987
45 transactions · 40 stateful · 2026-07-02 14:21:23 UTC
Parallelism
62/100
Blocked
57%
Avg conflicts / tx
2.42
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #85,128,987 · 45 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w27w08w112w017w018w119w220w321w422w523w624w725w835w238w139w1440w1541w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0x587911c7…9e01
0x34b655…2a6f
18 touches
36 conflicts
0xbcad2b5b…cc00
0x34b655…2a6f
18 touches
36 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
18 touches
36 conflicts
0x7d248840…6b0f
0x34b655…2a6f
16 touches
28 conflicts
0x9966da31…0d0f
0x34b655…2a6f
16 touches
28 conflicts
0x922c7ebd…6600
0xc8689a…ee79
16 touches
28 conflicts
0xf7e59d30…11dd
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
78 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity