← previous blocknext block →recent activity
Analyzing
Block #105,619,366
24 transactions · 21 stateful · 2026-09-17 13:38:49 UTC
Parallelism
58/100
Blocked
52%
Avg conflicts / tx
1.21
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,619,366 · 24 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
1w02w13w24w35w46w57w69w015w616w717w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf652e6d1…2a41
0xd32edf…ff58
13 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x0a85a226…83bd
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
21 conflicts on slot 0xf652e6d112…4f2a41
Audit this contract →
← previous block·next block →recent activity