← previous blocknext block →recent activity
Analyzing
Block #85,352,979
66 transactions · 57 stateful · 2026-07-03 15:13:29 UTC
Parallelism
71/100
Blocked
82%
Avg conflicts / tx
3.64
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #85,352,979 · 66 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w17w211w512w613w314w417w720w822w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
30 touches
105 conflicts
0x74b67e62…6912
0xd32edf…ff58
19 touches
45 conflicts
0xa29182a1…c12c
0x34b655…2a6f
18 touches
36 conflicts
0x342a12bc…c045
0x34b655…2a6f
14 touches
21 conflicts
0x7c6a17fa…e95d
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
14 touches
21 conflicts
0x1da60af2…3010
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
105 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity