← previous blocknext block →recent activity
Analyzing
Block #99,329,375
105 transactions · 55 stateful · 2026-08-26 12:30:30 UTC
Parallelism
77/100
Blocked
75%
Avg conflicts / tx
2.24
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #99,329,375 · 105 txs across 24 waves · depth 24
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w658w1064w1366w1470w1571w1672w1780w1888w1994w20
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94624b24…b277
0xd32edf…ff58
31 touches
120 conflicts
0x889d5e90…929a
0x2a68ba…90c5
26 touches
78 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002d
0x1b6862…e19c
16 touches
28 conflicts
0x3293a887…4402
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 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
120 conflicts on slot 0x94624b24eb…79b277
Audit this contract →
← previous block·next block →recent activity