← previous blocknext block →recent activity
Analyzing
Block #106,944,209
52 transactions · 44 stateful · 2026-09-22 04:50:15 UTC
Parallelism
58/100
Blocked
70%
Avg conflicts / tx
3.62
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #106,944,209 · 52 txs across 22 waves · depth 22
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w47w58w69w710w811w912w1013w1114w1218w1319w1433w1534w1635w1741w1544w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe5aada6…2578
0xd32edf…ff58
35 touches
153 conflicts
0x00000000…0015
0x1b6862…e19c
24 touches
66 conflicts
0xb1526c23…f2b9
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0013
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0012
0x1b6862…e19c
22 touches
55 conflicts
0x00000000…001d
0x1b6862…e19c
22 touches
55 conflicts
0x00000000…002d
0x1b6862…e19c
22 touches
55 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
22 touches
55 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
153 conflicts on slot 0xfe5aada6af…942578
Audit this contract →
← previous block·next block →recent activity