← previous blocknext block →recent activity
Analyzing
Block #85,134,558
17 transactions · 16 stateful · 2026-07-02 14:58:35 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,134,558 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w27w38w49w512w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67d8b378…f2f8
0x34b655…2a6f
10 touches
10 conflicts
0x264f7d7d…8444
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x286711a5…b3bf
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x1a28e34b…1404
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x7506443a…4820
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x67d8b378d2…4df2f8
Audit this contract →
← previous block·next block →recent activity