← previous blocknext block →recent activity
Analyzing
Block #87,752,748
25 transactions · 21 stateful · 2026-07-14 18:22:09 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
1.12
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,752,748 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w07w110w212w313w414w517w618w719w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5deef6f…6c3f
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x0960ac51…5440
0x34b655…2a6f
6 touches
3 conflicts
0x28504822…ded6
0x34b655…2a6f
6 touches
3 conflicts
0x46870010…0b51
0x34b655…2a6f
6 touches
3 conflicts
0x5f251b96…6054
0x34b655…2a6f
6 touches
3 conflicts
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 0xa5deef6f49…976c3f
Audit this contract →
← previous block·next block →recent activity