← previous blocknext block →recent activity
Analyzing
Block #98,333,278
21 transactions · 18 stateful · 2026-08-23 00:15:46 UTC
Parallelism
86/100
Blocked
44%
Avg conflicts / tx
0.52
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,333,278 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w15w07w09w111w112w213w014w015w118w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fd72f33…199d
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x0f94ee4c…1898
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x3a921be0…779c
0x2a68ba…90c5
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
3 conflicts on slot 0x6fd72f33cf…b9199d
Audit this contract →
← previous block·next block →recent activity