← previous blocknext block →recent activity
Analyzing
Block #99,253,319
57 transactions · 39 stateful · 2026-08-26 06:07:50 UTC
Parallelism
70/100
Blocked
79%
Avg conflicts / tx
2.72
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #99,253,319 · 57 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w820w122w923w1040w941w1042w1143w1244w1345w1447w1550w153w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd93ffba3…61d3
0xd32edf…ff58
31 touches
120 conflicts
0xba38536d…2b7d
0x065c9d…c394
10 touches
10 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
10 touches
10 conflicts
0x00000000…0000
0x63e48b…53f2
10 touches
10 conflicts
0x9a555477…19a8
0x754704…b603
10 touches
10 conflicts
0x00000000…0004
0x63e48b…53f2
10 touches
10 conflicts
0xba5743c7…21c2
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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
120 conflicts on slot 0xd93ffba3ec…6e61d3
Audit this contract →
← previous block·next block →recent activity