← previous blocknext block →recent activity
Analyzing
Block #98,434,696
23 transactions · 23 stateful · 2026-08-23 08:46:00 UTC
Parallelism
74/100
Blocked
57%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,434,696 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w19w010w111w212w013w114w215w016w118w220w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd668d8ce…6e33
0xd32edf…ff58
11 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x88e92ec7…696d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xbb3f3c…e046
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x64e1f0ce…7159
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
15 conflicts on slot 0xd668d8ce18…8d6e33
Audit this contract →
← previous block·next block →recent activity