← previous blocknext block →recent activity
Analyzing
Block #88,340,506
18 transactions · 16 stateful · 2026-07-17 11:53:58 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,340,506 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w29w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf7640726…19a2
0x2a68ba…90c5
8 touches
6 conflicts
0x7a12283f…b18a
0x2b46c0…1669
8 touches
6 conflicts
0x8649e48f…941c
0xc8689a…ee79
8 touches
6 conflicts
0x915c095e…c1e5
0x2b46c0…1669
8 touches
6 conflicts
0xcfe06a18…b5b5
0x2b46c0…1669
8 touches
6 conflicts
0x799aea28…88dc
0x851145…3f07
8 touches
6 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: 0x851145ea…9f3f07
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity