← previous blocknext block →recent activity
Analyzing
Block #85,135,339
20 transactions · 19 stateful · 2026-07-02 15:03:48 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
1.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,135,339 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w18w29w310w411w512w613w717w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb0cefcb…0d61
0x34b655…2a6f
16 touches
28 conflicts
0xf2112d98…bb04
0x34b655…2a6f
16 touches
28 conflicts
0x922c7ebd…6600
0xc8689a…ee79
14 touches
21 conflicts
0x7506443a…4820
0x34b655…2a6f
14 touches
21 conflicts
0x86a21cf9…a53b
0x34b655…2a6f
14 touches
21 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
14 touches
21 conflicts
0xd3ef5630…0de9
0x34b655…2a6f
14 touches
21 conflicts
0xd96c7369…a2c6
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
28 conflicts on slot 0xcb0cefcb67…d50d61
Audit this contract →
← previous block·next block →recent activity