← previous blocknext block →recent activity
Analyzing
Block #105,643,290
51 transactions · 42 stateful · 2026-09-17 15:39:16 UTC
Parallelism
61/100
Blocked
76%
Avg conflicts / tx
4.16
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #105,643,290 · 51 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1315w816w920w1422w1534w1636w1737w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c369081…0cdc
0xd32edf…ff58
37 touches
171 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0012
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0013
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0015
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…001b
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…002b
0x1b6862…e19c
24 touches
66 conflicts
0xd996735f…8731
0x1b6862…e19c
24 touches
66 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
171 conflicts on slot 0x5c36908139…900cdc
Audit this contract →
← previous block·next block →recent activity