← previous blocknext block →recent activity
Analyzing
Block #87,409,365
24 transactions · 21 stateful · 2026-07-13 04:04:48 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,409,365 · 24 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
3w04w06w07w18w29w310w411w112w213w114w416w322w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x69ce640b…884a
0x34b655…2a6f
8 touches
6 conflicts
0x0eeb2a30…6909
0x34b655…2a6f
6 touches
3 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
6 touches
3 conflicts
0x43ad51e0…365b
0x34b655…2a6f
4 touches
1 conflict
0x49f4c464…01aa
0x34b655…2a6f
4 touches
1 conflict
0x56b580bf…f969
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity