← previous blocknext block →recent activity
Analyzing
Block #98,847,629
35 transactions · 25 stateful · 2026-08-24 20:00:03 UTC
Parallelism
86/100
Blocked
40%
Avg conflicts / tx
0.49
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,847,629 · 35 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
1w02w13w24w39w010w116w018w119w421w428w029w130w231w032w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd359baff…c70b
0xd32edf…ff58
9 touches
10 conflicts
0xf79df061…e005
0xe52b14…7230
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
0xd18a8dca…452c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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 0xd359baff4e…bdc70b
Audit this contract →
← previous block·next block →recent activity