← previous blocknext block →recent activity
Analyzing
Block #98,327,576
25 transactions · 24 stateful · 2026-08-22 23:47:05 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
1.84
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #98,327,576 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w611w612w718w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf602a1b1…63f8
0xd32edf…ff58
17 touches
36 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x35801c67…bcbf
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
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
36 conflicts on slot 0xf602a1b1f1…df63f8
Audit this contract →
← previous block·next block →recent activity