← previous blocknext block →recent activity
Analyzing
Block #87,913,153
23 transactions · 19 stateful · 2026-07-15 12:15:05 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
1.09
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,913,153 · 23 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
1w02w13w24w35w49w013w015w116w217w318w421w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf28cf8dc…b0ca
0x34b655…2a6f
10 touches
10 conflicts
0x337647c0…b410
0xd32edf…ff58
9 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x9ba6ae4a…90cb
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 0xf28cf8dcba…4ab0ca
Audit this contract →
← previous block·next block →recent activity