← previous blocknext block →recent activity
Analyzing
Block #98,539,280
24 transactions · 16 stateful · 2026-08-23 17:39:59 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.25
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,539,280 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77bb0f5d…9652
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x6c6f37ba…c20a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xd28e195f…37a1
0x34b655…2a6f
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
28 conflicts on slot 0x77bb0f5d55…3b9652
Audit this contract →
← previous block·next block →recent activity