← previous blocknext block →recent activity
Analyzing
Block #99,288,301
23 transactions · 21 stateful · 2026-08-26 09:03:54 UTC
Parallelism
70/100
Blocked
48%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,288,301 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w49w510w012w513w614w119w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4351a382…d323
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0xc75a1e50…214a
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
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
21 conflicts on slot 0x4351a38295…f8d323
Audit this contract →
← previous block·next block →recent activity