← previous blocknext block →recent activity
Analyzing
Block #98,458,956
48 transactions · 44 stateful · 2026-08-23 10:48:15 UTC
Parallelism
83/100
Blocked
59%
Avg conflicts / tx
1.77
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,458,956 · 48 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w324w426w427w528w629w735w336w438w145w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b26100f…3500
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0002
0xbb3f3c…e046
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001c
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002c
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0xf58eca50…59fa
0x1b6862…e19c
12 touches
15 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
28 conflicts on slot 0x0b26100fa4…db3500
Audit this contract →
← previous block·next block →recent activity