← previous blocknext block →recent activity
Analyzing
Block #87,588,051
27 transactions · 24 stateful · 2026-07-14 00:00:34 UTC
Parallelism
78/100
Blocked
58%
Avg conflicts / tx
1.3
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,588,051 · 27 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
1w02w14w26w07w18w09w110w111w212w313w414w523w324w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59dccbd8…2bf6
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0x2f702750…347d
0x34b655…2a6f
6 touches
3 conflicts
0x48b72f1b…46e6
0x34b655…2a6f
6 touches
3 conflicts
0x4d9858eb…7098
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x691e3505…dd2f
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
10 conflicts on slot 0x59dccbd857…c52bf6
Audit this contract →
← previous block·next block →recent activity