← previous blocknext block →recent activity
Analyzing
Block #98,101,306
30 transactions · 22 stateful · 2026-08-22 04:47:58 UTC
Parallelism
90/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,101,306 · 30 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
1w02w13w06w07w110w011w112w013w119w229w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf50c5290…54a3
0xd32edf…ff58
5 touches
3 conflicts
0x9b6fad3c…8b92
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c3
0x1b6862…e19c
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 0xf50c5290c5…a454a3
Audit this contract →
← previous block·next block →recent activity