← previous blocknext block →recent activity
Analyzing
Block #109,133,095
21 transactions · 18 stateful · 2026-09-29 20:36:54 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,133,095 · 21 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
1w02w13w24w35w47w08w110w011w112w213w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x522a1dae…09e8
0xd32edf…ff58
9 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x05006bd2…56ea
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c4
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c5
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c6
0x508254…98bd
4 touches
1 conflict
0x4ea2b33b…7dbc
0x508254…98bd
4 touches
1 conflict
0x00000000…0003
0x125f12…a50b
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 0x522a1dae53…b009e8
Audit this contract →
← previous block·next block →recent activity