← previous blocknext block →recent activity
Analyzing
Block #101,069,783
31 transactions · 28 stateful · 2026-09-01 14:47:39 UTC
Parallelism
68/100
Blocked
79%
Avg conflicts / tx
1.94
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #101,069,783 · 31 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
1w02w13w24w37w39w311w413w414w315w516w618w427w628w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40e7f936…89ca
0xd32edf…ff58
13 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x3f2100d8…f9b5
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…0012
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 0x40e7f9366c…9389ca
Audit this contract →
← previous block·next block →recent activity