← previous blocknext block →recent activity
Analyzing
Block #87,910,066
18 transactions · 16 stateful · 2026-07-15 11:54:26 UTC
Parallelism
72/100
Blocked
31%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,910,066 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w110w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76d36e11…fde2
0x34b655…2a6f
6 touches
3 conflicts
0x364289f7…f98a
0x34b655…2a6f
6 touches
3 conflicts
0x3f7d8a09…362c
0x34b655…2a6f
6 touches
3 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
6 touches
3 conflicts
0x2965e2d6…5800
0x34b655…2a6f
4 touches
1 conflict
0x33da0dfa…bac6
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x4426bf1e…532a
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 0x76d36e11cd…6afde2
Audit this contract →
← previous block·next block →recent activity