← previous blocknext block →recent activity
Analyzing
Block #99,020,713
25 transactions · 25 stateful · 2026-08-25 10:32:42 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,020,713 · 25 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
1w02w13w24w35w46w57w612w518w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ffa40b0…8adc
0xd32edf…ff58
15 touches
28 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
6 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
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…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
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
28 conflicts on slot 0x5ffa40b0a1…898adc
Audit this contract →
← previous block·next block →recent activity