← previous blocknext block →recent activity
Analyzing
Block #105,929,184
70 transactions · 57 stateful · 2026-09-18 15:40:29 UTC
Parallelism
89/100
Blocked
53%
Avg conflicts / tx
1.29
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,929,184 · 70 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w08w19w210w311w016w117w223w124w434w536w140w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0ed5b1c…770e
0xd32edf…ff58
13 touches
21 conflicts
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xeab76d19…a378
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 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
21 conflicts on slot 0xb0ed5b1cca…67770e
Audit this contract →
← previous block·next block →recent activity