← previous blocknext block →recent activity
Analyzing
Block #98,014,206
20 transactions · 19 stateful · 2026-08-21 21:29:32 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,014,206 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w07w010w312w413w114w016w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb29c1593…3210
0xd32edf…ff58
9 touches
10 conflicts
0xd59f6ed1…03e7
0x1b6862…e19c
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x19bd8142…f7ed
0x40c49f…2af0
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
10 conflicts on slot 0xb29c159374…b43210
Audit this contract →
← previous block·next block →recent activity