← previous blocknext block →recent activity
Analyzing
Block #87,717,600
67 transactions · 49 stateful · 2026-07-14 14:27:03 UTC
Parallelism
76/100
Blocked
63%
Avg conflicts / tx
2.19
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,717,600 · 67 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w09w110w212w313w414w015w119w131w032w133w234w335w436w537w638w752w353w556w557w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
26 touches
78 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
14 touches
21 conflicts
0x7525206c…fbd5
0x34b655…2a6f
14 touches
21 conflicts
0x13510de3…1c68
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
10 touches
10 conflicts
0x67905f6e…02a1
0x34b655…2a6f
10 touches
10 conflicts
0x6a1604d1…3e8a
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
78 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity