← previous blocknext block →recent activity
Analyzing
Block #85,123,730
20 transactions · 19 stateful · 2026-07-02 13:46:14 UTC
Parallelism
65/100
Blocked
42%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,123,730 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w510w615w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0x50dea9f9…636e
0x34b655…2a6f
10 touches
10 conflicts
0x5d7f309d…5145
0x34b655…2a6f
10 touches
10 conflicts
0x8967ba26…9962
0x34b655…2a6f
10 touches
10 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
10 touches
10 conflicts
0xabd0fca8…b1d4
0x34b655…2a6f
10 touches
10 conflicts
0xbc8ead31…90fd
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity