← previous blocknext block →recent activity
Analyzing
Block #105,853,410
36 transactions · 33 stateful · 2026-09-18 09:18:14 UTC
Parallelism
75/100
Blocked
61%
Avg conflicts / tx
1.81
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,853,410 · 36 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w825w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf380a905…3f27
0xd32edf…ff58
17 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0x1045386d…cb8d
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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
36 conflicts on slot 0xf380a90561…ba3f27
Audit this contract →
← previous block·next block →recent activity