← previous blocknext block →recent activity
Analyzing
Block #88,365,113
22 transactions · 22 stateful · 2026-07-17 14:39:18 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.59
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #88,365,113 · 22 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
2w05w16w211w212w313w416w517w618w719w820w921w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x8e4fdba3…18f1
0x34b655…2a6f
8 touches
6 conflicts
0x86977b3d…a9c4
0x34b655…2a6f
8 touches
6 conflicts
0xb988c952…a33e
0x34b655…2a6f
8 touches
6 conflicts
0x140eb1ca…bc07
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
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 0x2d65195682…4112e8
Audit this contract →
← previous block·next block →recent activity