← previous blocknext block →recent activity
Analyzing
Block #85,139,729
16 transactions · 16 stateful · 2026-07-02 15:33:07 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,139,729 · 16 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
3w04w15w26w37w49w112w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67d8b378…f2f8
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xc99e7125…81b1
0x34b655…2a6f
8 touches
6 conflicts
0xe47478a3…a058
0x34b655…2a6f
6 touches
3 conflicts
0xaa48195d…ffee
0x34b655…2a6f
6 touches
3 conflicts
0xf3fbc9b8…ab58
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 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