← previous blocknext block →recent activity
Analyzing
Block #98,380,016
30 transactions · 23 stateful · 2026-08-23 04:10:54 UTC
Parallelism
87/100
Blocked
48%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,380,016 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w08w19w216w319w320w021w023w124w225w026w128w129w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1ef4d4a…c2ec
0xd32edf…ff58
7 touches
6 conflicts
0xd53220ed…4736
0x1b6862…e19c
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…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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
6 conflicts on slot 0xf1ef4d4a39…22c2ec
Audit this contract →
← previous block·next block →recent activity