← previous blocknext block →recent activity
Analyzing
Block #87,911,117
21 transactions · 19 stateful · 2026-07-15 12:01:28 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,911,117 · 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
1w02w13w16w27w38w411w012w514w115w620w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72880226…1435
0x34b655…2a6f
12 touches
15 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0x95c9704c…8a57
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4a4
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 0x7288022679…181435
Audit this contract →
← previous block·next block →recent activity