← previous blocknext block →recent activity
Analyzing
Block #106,206,733
40 transactions · 35 stateful · 2026-09-19 14:57:30 UTC
Parallelism
80/100
Blocked
63%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,206,733 · 40 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w631w132w633w739w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ddae4a1…feba
0xd32edf…ff58
13 touches
21 conflicts
0x1159e370…0284
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x394c3833…b4ae
0x1b6862…e19c
8 touches
6 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
21 conflicts on slot 0x0ddae4a1a2…d1feba
Audit this contract →
← previous block·next block →recent activity