← previous blocknext block →recent activity
Analyzing
Block #98,851,251
23 transactions · 21 stateful · 2026-08-24 20:18:17 UTC
Parallelism
65/100
Blocked
57%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,851,251 · 23 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
1w02w13w24w35w47w28w59w013w014w116w417w618w722w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05192ab0…b70e
0xd32edf…ff58
9 touches
10 conflicts
0xf823e97f…2ee6
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x3a3097d7…2ab5
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
10 conflicts on slot 0x05192ab0fe…1db70e
Audit this contract →
← previous block·next block →recent activity