← previous blocknext block →recent activity
Analyzing
Block #85,751,305
20 transactions · 16 stateful · 2026-07-05 11:27:07 UTC
Parallelism
60/100
Blocked
63%
Avg conflicts / tx
1.75
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,751,305 · 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
3w04w15w26w37w48w59w616w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
14 touches
21 conflicts
0x342fbbca…d443
0x40c49f…2af0
12 touches
15 conflicts
0x53e50026…6d8c
0x69df8a…6292
10 touches
10 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
10 touches
10 conflicts
0x46279ae7…20dd
0x69df8a…6292
10 touches
10 conflicts
0x213ee207…a151
0x69df8a…6292
10 touches
10 conflicts
0x7f4a8466…f2cc
0x69df8a…6292
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: 0x40c49f17…d22af0
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity