← previous blocknext block →recent activity
Analyzing
Block #98,551,528
36 transactions · 32 stateful · 2026-08-23 18:43:58 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
1.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,551,528 · 36 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
1w02w13w29w013w314w415w516w620w121w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6689e569…7c2a
0xd32edf…ff58
15 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x0f94ee4c…189c
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
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
28 conflicts on slot 0x6689e569b6…057c2a
Audit this contract →
← previous block·next block →recent activity