← previous blocknext block →recent activity
Analyzing
Block #87,751,520
20 transactions · 19 stateful · 2026-07-14 18:13:57 UTC
Parallelism
70/100
Blocked
32%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,751,520 · 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
5w06w18w211w012w114w315w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59dccbd8…2bf6
0x34b655…2a6f
12 touches
15 conflicts
0x2fdfe038…c16c
0x34b655…2a6f
8 touches
6 conflicts
0x20317244…edb4
0x34b655…2a6f
6 touches
3 conflicts
0x6e088aaa…3972
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x5f251b96…6054
0x34b655…2a6f
4 touches
1 conflict
0x67decb02…f8e8
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 0x59dccbd857…c52bf6
Audit this contract →
← previous block·next block →recent activity