← previous blocknext block →recent activity
Analyzing
Block #87,689,606
23 transactions · 23 stateful · 2026-07-14 11:19:25 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,689,606 · 23 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
3w04w16w07w112w014w115w116w217w318w019w220w322w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xbcc5ae85…6ba2
0xa6afd3…d132
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
6 touches
3 conflicts
0x529110cf…1128
0x34b655…2a6f
4 touches
1 conflict
0x6483a537…b63e
0x34b655…2a6f
4 touches
1 conflict
0x6483a537…b63f
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity