← previous blocknext block →recent activity
Analyzing
Block #99,366,199
22 transactions · 18 stateful · 2026-08-26 15:35:59 UTC
Parallelism
77/100
Blocked
39%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,366,199 · 22 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
1w02w13w24w36w18w09w010w416w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f85fac2…3283
0xd32edf…ff58
7 touches
6 conflicts
0x9378abf5…ee79
0x3bd359…433a
6 touches
3 conflicts
0x70ee5ee3…ff93
0x350035…7777
6 touches
3 conflicts
0x00000000…0008
0x0a6325…bcfc
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x6aa624fd…a851
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
6 conflicts on slot 0x3f85fac25a…e23283
Audit this contract →
← previous block·next block →recent activity