← previous blocknext block →recent activity
Analyzing
Block #98,567,953
28 transactions · 28 stateful · 2026-08-23 20:09:49 UTC
Parallelism
82/100
Blocked
32%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,567,953 · 28 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
1w02w13w24w36w07w18w09w413w416w218w123w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd0eb3bd…a1c1
0xd32edf…ff58
9 touches
10 conflicts
0xffe431af…8faa
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…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xb538c6fa…9aeb
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
10 conflicts on slot 0xdd0eb3bd2e…b4a1c1
Audit this contract →
← previous block·next block →recent activity