← previous blocknext block →recent activity
Analyzing
Block #98,473,106
23 transactions · 20 stateful · 2026-08-23 11:59:36 UTC
Parallelism
57/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #98,473,106 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w611w712w820w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x213bedd1…a5ce
0xd32edf…ff58
13 touches
21 conflicts
0x5a95f394…be66
0x34b655…2a6f
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…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x07b5c6c6…8867
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
21 conflicts on slot 0x213bedd1b5…2ea5ce
Audit this contract →
← previous block·next block →recent activity