← previous blocknext block →recent activity
Analyzing
Block #106,164,541
190 transactions · 101 stateful · 2026-09-19 11:25:08 UTC
Parallelism
92/100
Blocked
82%
Avg conflicts / tx
1.95
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,164,541 · 190 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w010w011w112w213w314w415w516w624w125w226w333w734w836w139w291w493w5107w9116w6126w9166w10168w11183w6184w7187w13189w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb17ab549…51b2
0xd32edf…ff58
25 touches
78 conflicts
0x00000000…0002
0xf5b5f7…6d70
24 touches
66 conflicts
0xaad6be10…0801
0x2a68ba…90c5
18 touches
36 conflicts
0x33fa06a2…87b1
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…00c9
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
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
78 conflicts on slot 0xb17ab54963…2651b2
Audit this contract →
← previous block·next block →recent activity