← previous blocknext block →recent activity
Analyzing
Block #87,716,364
31 transactions · 27 stateful · 2026-07-14 14:18:43 UTC
Parallelism
74/100
Blocked
59%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,716,364 · 31 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w59w013w014w115w216w319w220w325w526w629w630w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7eb90864…574d
0x34b655…2a6f
10 touches
10 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x59d095e0…98a7
0xd32edf…ff58
7 touches
6 conflicts
0x5bb46f6c…7693
0x34b655…2a6f
6 touches
3 conflicts
0x3b9bb58c…e73a
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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 0x7eb9086438…db574d
Audit this contract →
← previous block·next block →recent activity