← previous blocknext block →recent activity
Analyzing
Block #98,457,417
30 transactions · 24 stateful · 2026-08-23 10:40:29 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.33
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #98,457,417 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w613w115w718w825w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38ad24e4…251f
0xd32edf…ff58
17 touches
36 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xf8480e2a…dff2
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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
36 conflicts on slot 0x38ad24e4bb…61251f
Audit this contract →
← previous block·next block →recent activity