← previous blocknext block →recent activity
Analyzing
Block #87,911,821
26 transactions · 15 stateful · 2026-07-15 12:06:10 UTC
Parallelism
85/100
Blocked
47%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,911,821 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w19w011w115w116w217w218w323w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f35c56f…046b
0x34b655…2a6f
6 touches
3 conflicts
0x147259c6…1709
0x34b655…2a6f
4 touches
1 conflict
0x2d1d07e4…eeda
0x34b655…2a6f
4 touches
1 conflict
0x30ab53da…3529
0x34b655…2a6f
4 touches
1 conflict
0x49f5a697…72c0
0x34b655…2a6f
4 touches
1 conflict
0x4cee015b…1a5e
0x34b655…2a6f
4 touches
1 conflict
0x64a058c6…74a1
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
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
3 conflicts on slot 0x2f35c56f7b…bd046b
Audit this contract →
← previous block·next block →recent activity