← previous blocknext block →recent activity
Analyzing
Block #98,764,779
40 transactions · 34 stateful · 2026-08-24 13:03:01 UTC
Parallelism
80/100
Blocked
62%
Avg conflicts / tx
1.45
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,764,779 · 40 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
1w02w13w24w35w313w114w427w528w529w631w737w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22a4c869…c5f8
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0002
0xbb3f3c…e046
10 touches
10 conflicts
0x00000000…002a
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…001a
0x1b6862…e19c
8 touches
6 conflicts
0xc13fac9b…d2d0
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
28 conflicts on slot 0x22a4c8698e…c4c5f8
Audit this contract →
← previous block·next block →recent activity