← previous blocknext block →recent activity
Analyzing
Block #109,177,172
30 transactions · 24 stateful · 2026-09-30 00:19:06 UTC
Parallelism
70/100
Blocked
63%
Avg conflicts / tx
1.6
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #109,177,172 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w717w819w322w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b46540d…2d9d
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0xfac61869…a55d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002a
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0040
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0053
0x1b6862…e19c
14 touches
21 conflicts
0xbff401a6…b269
0x1b6862…e19c
14 touches
21 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 0x6b46540db4…0b2d9d
Audit this contract →
← previous block·next block →recent activity