← previous blocknext block →recent activity
Analyzing
Block #106,252,956
20 transactions · 18 stateful · 2026-09-19 18:50:12 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,252,956 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w110w011w012w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd04764a8…7de9
0xd32edf…ff58
9 touches
10 conflicts
0x2642468f…6d81
0x34b655…2a6f
4 touches
1 conflict
0x27826bde…1da4
0x34b655…2a6f
4 touches
1 conflict
0x366a19b0…f065
0x34b655…2a6f
4 touches
1 conflict
0x75f928fc…0465
0x34b655…2a6f
4 touches
1 conflict
0x839c0c71…bada
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0x9167c873…748f
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0xd04764a806…f27de9
Audit this contract →
← previous block·next block →recent activity