← previous blocknext block →recent activity
Analyzing
Block #98,564,270
37 transactions · 26 stateful · 2026-08-23 19:50:30 UTC
Parallelism
84/100
Blocked
46%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,564,270 · 37 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
1w07w19w010w214w217w118w219w320w421w525w026w131w133w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dc489f4…10cf
0xd32edf…ff58
11 touches
15 conflicts
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
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 0x9dc489f471…c010cf
Audit this contract →
← previous block·next block →recent activity