← previous blocknext block →recent activity
Analyzing
Block #87,730,868
20 transactions · 17 stateful · 2026-07-14 15:55:47 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,730,868 · 20 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
2w03w04w15w16w29w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe40c96f3…9ce4
0x34b655…2a6f
6 touches
3 conflicts
0xc9bfa286…086a
0x34b655…2a6f
6 touches
3 conflicts
0x7fb99184…e8bb
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x50718952…7c75
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xfffe583a…9130
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 0xe40c96f301…1b9ce4
Audit this contract →
← previous block·next block →recent activity