← previous blocknext block →recent activity
Analyzing
Block #106,954,020
62 transactions · 49 stateful · 2026-09-22 05:39:39 UTC
Parallelism
71/100
Blocked
78%
Avg conflicts / tx
3.29
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #106,954,020 · 62 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w29w310w211w112w213w314w415w516w621w740w841w942w1143w1244w1346w348w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f174261…4530
0xd32edf…ff58
25 touches
78 conflicts
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001d
0x1b6862…e19c
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x1d81790c…b9f7
0x34b655…2a6f
14 touches
21 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 0x0f174261d1…944530
Audit this contract →
← previous block·next block →recent activity