← previous blocknext block →recent activity
Analyzing
Block #98,606,230
26 transactions · 23 stateful · 2026-08-23 23:29:15 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,606,230 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w16w313w415w516w017w618w120w021w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4238d7c…4466
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x3f2100d8…f9b5
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
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 0xa4238d7ce4…3a4466
Audit this contract →
← previous block·next block →recent activity