← previous blocknext block →recent activity
Analyzing
Block #96,701,112
26 transactions · 23 stateful · 2026-08-17 06:11:24 UTC
Parallelism
81/100
Blocked
61%
Avg conflicts / tx
1.15
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,701,112 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w27w18w29w310w411w012w113w214w017w120w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x437039a3…ec5b
0xd32edf…ff58
9 touches
10 conflicts
0x6bdb9869…7558
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x103de0…bb55
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
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
10 conflicts on slot 0x437039a36d…4bec5b
Audit this contract →
← previous block·next block →recent activity