← previous blocknext block →recent activity
Analyzing
Block #98,740,049
40 transactions · 28 stateful · 2026-08-24 10:58:28 UTC
Parallelism
75/100
Blocked
57%
Avg conflicts / tx
1.25
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #98,740,049 · 40 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w616w123w726w839w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf527df47…6454
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x3293a887…43fe
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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 0xf527df47e7…4f6454
Audit this contract →
← previous block·next block →recent activity