← previous blocknext block →recent activity
Analyzing
Block #87,737,427
20 transactions · 19 stateful · 2026-07-14 16:39:39 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,737,427 · 20 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
1w02w13w24w25w37w08w19w212w213w314w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9f59232…f58c
0x34b655…2a6f
12 touches
15 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x76d36e11…fde2
0x34b655…2a6f
6 touches
3 conflicts
0x7edfb3fa…4aec
0xd32edf…ff58
5 touches
3 conflicts
0x7048d42f…288b
0x34b655…2a6f
4 touches
1 conflict
0x75d2b8f6…a34d
0x34b655…2a6f
4 touches
1 conflict
0x680ca7d7…2df4
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
15 conflicts on slot 0xa9f59232f9…53f58c
Audit this contract →
← previous block·next block →recent activity