← previous blocknext block →recent activity
Analyzing
Block #109,237,284
11 transactions · 11 stateful · 2026-09-30 05:21:40 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #109,237,284 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1cb03b…515d
0xd32edf…ff58
7 touches
6 conflicts
0x11998eac…f9a2
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0040
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0054
0x1b6862…e19c
4 touches
1 conflict
0x09d0c090…d60d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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
6 conflicts on slot 0xba1cb03b8e…cc515d
Audit this contract →
← previous block·next block →recent activity