← previous blocknext block →recent activity
Analyzing
Block #88,355,598
33 transactions · 28 stateful · 2026-07-17 13:35:07 UTC
Parallelism
67/100
Blocked
64%
Avg conflicts / tx
1.39
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #88,355,598 · 33 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w28w010w112w013w114w215w316w419w322w223w524w629w730w831w932w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xfb874a6c…caa0
0x34b655…2a6f
8 touches
6 conflicts
0xf565ea1f…4245
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x0e525f1d…dfed
0x34b655…2a6f
6 touches
3 conflicts
0x3413a430…234a
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity