← previous blocknext block →recent activity
Analyzing
Block #109,234,547
18 transactions · 17 stateful · 2026-09-30 05:07:53 UTC
Parallelism
50/100
Blocked
71%
Avg conflicts / tx
2.33
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #109,234,547 · 18 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
1w02w13w24w35w46w58w69w717w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf81d1ab1…94d0
0xd32edf…ff58
17 touches
36 conflicts
0x6d43ee99…bdd6
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0xee10f36a…f1ee
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0040
0x1b6862…e19c
10 touches
10 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 0xf81d1ab1c3…d094d0
Audit this contract →
← previous block·next block →recent activity