← previous blocknext block →recent activity
Analyzing
Block #99,074,531
24 transactions · 23 stateful · 2026-08-25 15:07:50 UTC
Parallelism
83/100
Blocked
52%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,074,531 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w07w09w111w114w315w216w118w319w221w323w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d86281d…2a76
0xd32edf…ff58
7 touches
6 conflicts
0x4d42f16e…a6c6
0x1b6862…e19c
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
0x00000000…003d
0x065c9d…c394
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
6 conflicts on slot 0x5d86281d5b…9e2a76
Audit this contract →
← previous block·next block →recent activity