← previous blocknext block →recent activity
Analyzing
Block #106,395,258
62 transactions · 49 stateful · 2026-09-20 06:46:19 UTC
Parallelism
60/100
Blocked
84%
Avg conflicts / tx
5.47
Longest chain
25 deep
Execution timeline
did this block parallelize well?
view
block #106,395,258 · 62 txs across 25 waves · depth 25
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
wave w24
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w612w713w814w137w1238w1353w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x622a32db…be35
0xd32edf…ff58
33 touches
136 conflicts
0xca841faa…486a
0x34b655…2a6f
32 touches
120 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
26 touches
78 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
26 touches
78 conflicts
0x00000000…0012
0x1b6862…e19c
26 touches
78 conflicts
0x00000000…001a
0x1b6862…e19c
26 touches
78 conflicts
0xc824469a…6425
0x34b655…2a6f
24 touches
66 conflicts
0x482471ad…122f
0x34b655…2a6f
18 touches
36 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
136 conflicts on slot 0x622a32dbfa…ccbe35
Audit this contract →
← previous block·next block →recent activity