← previous blocknext block →recent activity
Analyzing
Block #99,263,314
31 transactions · 26 stateful · 2026-08-26 06:58:13 UTC
Parallelism
84/100
Blocked
31%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,263,314 · 31 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
1w03w15w07w29w010w111w212w313w421w423w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01a64183…f493
0xd32edf…ff58
9 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x4233e455…0bfe
0x065c9d…c394
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x3a921be0…779c
0x2a68ba…90c5
4 touches
1 conflict
0xb8c65bc7…e8b5
0x3bd359…433a
4 touches
1 conflict
0xc9a5287f…6451
0x40c49f…2af0
3 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
10 conflicts on slot 0x01a64183a5…a3f493
Audit this contract →
← previous block·next block →recent activity