← previous blocknext block →recent activity
Analyzing
Block #106,041,215
24 transactions · 20 stateful · 2026-09-19 01:04:29 UTC
Parallelism
75/100
Blocked
60%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,041,215 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w18w011w212w113w114w217w318w420w521w222w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ac20326…2ff4
0xd32edf…ff58
11 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x65903ef9…2567
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x46279ae7…20dd
0x34ae4d…3fc5
2 touches
0 conflicts
0x53e50026…6d8c
0x34ae4d…3fc5
2 touches
0 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
15 conflicts on slot 0x9ac20326d2…942ff4
Audit this contract →
← previous block·next block →recent activity