← previous blocknext block →recent activity
Analyzing
Block #87,710,538
21 transactions · 18 stateful · 2026-07-14 13:39:38 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,710,538 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w07w110w111w212w314w415w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xff3dbbcd…5060
0x34b655…2a6f
6 touches
3 conflicts
0x461a3556…5948
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xa38eb2fc…1658
0x34b655…2a6f
6 touches
3 conflicts
0xa38eb2fc…1659
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 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity