← previous blocknext block →recent activity
Analyzing
Block #109,228,741
16 transactions · 14 stateful · 2026-09-30 04:38:40 UTC
Parallelism
38/100
Blocked
71%
Avg conflicts / tx
2.38
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #109,228,741 · 16 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x510bd1ce…2baa
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001b
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002b
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0040
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0054
0x1b6862…e19c
12 touches
15 conflicts
0x41629d02…0e45
0x1b6862…e19c
12 touches
15 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 0x510bd1cec9…9d2baa
Audit this contract →
← previous block·next block →recent activity