← previous blocknext block →recent activity
Analyzing
Block #96,696,098
20 transactions · 19 stateful · 2026-08-17 05:46:11 UTC
Parallelism
70/100
Blocked
63%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,696,098 · 20 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
1w02w13w24w35w46w37w48w511w413w514w416w317w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c3dfd95…26d2
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x17a7f697…dcb1
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
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: FastLane: FastLaneAuctionHandler
15 conflicts on slot 0x4c3dfd9536…f526d2
Audit this contract →
← previous block·next block →recent activity