← previous blocknext block →recent activity
Analyzing
Block #99,246,334
36 transactions · 23 stateful · 2026-08-26 05:32:42 UTC
Parallelism
86/100
Blocked
39%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,246,334 · 36 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
2w03w09w111w114w218w220w021w125w226w327w030w433w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf68726e1…6358
0xd32edf…ff58
9 touches
10 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x01e7b865…6e6e
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 0xf68726e1e9…186358
Audit this contract →
← previous block·next block →recent activity