← previous blocknext block →recent activity
Analyzing
Block #109,170,001
40 transactions · 33 stateful · 2026-09-29 23:43:01 UTC
Parallelism
75/100
Blocked
67%
Avg conflicts / tx
1.55
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #109,170,001 · 40 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
2w03w14w25w36w47w58w69w710w811w924w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60c666fb…a7d5
0xd32edf…ff58
19 touches
45 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0xcad937e9…786e
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0053
0x1b6862…e19c
14 touches
21 conflicts
0x4e4514f1…91ab
0x1b6862…e19c
14 touches
21 conflicts
0x62c1c504…ea5d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
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
45 conflicts on slot 0x60c666fbfd…3da7d5
Audit this contract →
← previous block·next block →recent activity