← previous blocknext block →recent activity
Analyzing
Block #88,365,884
21 transactions · 18 stateful · 2026-07-17 14:44:40 UTC
Parallelism
62/100
Blocked
50%
Avg conflicts / tx
1.29
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #88,365,884 · 21 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
1w02w13w24w35w16w48w212w513w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa55c4598…2988
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x427d1120…4eb1
0x34b655…2a6f
8 touches
6 conflicts
0xcc11c0f6…5670
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
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 0xa55c45989b…e52988
Audit this contract →
← previous block·next block →recent activity