← previous blocknext block →recent activity
Analyzing
Block #85,140,786
20 transactions · 20 stateful · 2026-07-02 15:40:10 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,140,786 · 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
7w08w19w210w311w412w514w015w016w118w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2112d98…bb04
0x34b655…2a6f
12 touches
15 conflicts
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0xffb8950c…23c6
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0x00df1127…6fe4
0x34b655…2a6f
10 touches
10 conflicts
0x295f8f9b…5bb5
0x34b655…2a6f
10 touches
10 conflicts
0x5b353877…605d
0x34b655…2a6f
10 touches
10 conflicts
0x7c0bdc54…9dde
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
15 conflicts on slot 0xf2112d985f…abbb04
Audit this contract →
← previous block·next block →recent activity