← previous blocknext block →recent activity
Analyzing
Block #98,770,771
51 transactions · 38 stateful · 2026-08-24 13:33:10 UTC
Parallelism
80/100
Blocked
63%
Avg conflicts / tx
1.16
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #98,770,771 · 51 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
1w02w13w24w35w49w413w414w328w533w534w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e6b708a…1ef3
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x41755291…977f
0x065c9d…c394
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…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
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
21 conflicts on slot 0x0e6b708a9c…741ef3
Audit this contract →
← previous block·next block →recent activity