← previous blocknext block →recent activity
Analyzing
Block #98,333,268
29 transactions · 20 stateful · 2026-08-23 00:15:43 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,333,268 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w07w110w011w115w016w117w218w320w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9660c616…f3ff
0xd32edf…ff58
7 touches
6 conflicts
0x5fb00fd2…2099
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x6d352690…6b75
0x3bd359…433a
4 touches
1 conflict
0x5164ab0e…01e1
0xc8689a…ee79
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
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 0x9660c61629…c5f3ff
Audit this contract →
← previous block·next block →recent activity