← previous blocknext block →recent activity
Analyzing
Block #88,355,509
35 transactions · 33 stateful · 2026-07-17 13:34:30 UTC
Parallelism
77/100
Blocked
70%
Avg conflicts / tx
1.74
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #88,355,509 · 35 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
1w02w13w24w35w46w59w620w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c6155c5…8558
0xd32edf…ff58
13 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x87ee379a…cd9e
0x34b655…2a6f
6 touches
3 conflicts
0xbbee202a…8912
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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: FastLane: FastLaneAuctionHandler
21 conflicts on slot 0x9c6155c56a…698558
Audit this contract →
← previous block·next block →recent activity