← previous blocknext block →recent activity
Analyzing
Block #99,200,680
24 transactions · 18 stateful · 2026-08-26 01:43:00 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,200,680 · 24 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
1w02w13w26w111w218w319w421w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x349b6312…38b2
0xd32edf…ff58
9 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x2274142b…f885
0x851145…3f07
4 touches
1 conflict
0x7ea2bdd4…b4b0
0x851145…3f07
4 touches
1 conflict
0x8b98c194…d69e
0x851145…3f07
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
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
10 conflicts on slot 0x349b63125d…6838b2
Audit this contract →
← previous block·next block →recent activity