← previous blocknext block →recent activity
Analyzing
Block #96,156,354
16 transactions · 13 stateful · 2026-08-15 08:31:13 UTC
Parallelism
63/100
Blocked
54%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,156,354 · 16 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
1w02w13w24w35w46w59w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f28470f…6e3c
0xd32edf…ff58
11 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0313ab1d…1e48
0x065c9d…c394
2 touches
0 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
2 touches
0 conflicts
0x00f7e3b7…e017
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 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
15 conflicts on slot 0x6f28470f46…036e3c
Audit this contract →
← previous block·next block →recent activity