← previous blocknext block →recent activity
Analyzing
Block #105,575,937
33 transactions · 32 stateful · 2026-09-17 10:00:12 UTC
Parallelism
76/100
Blocked
69%
Avg conflicts / tx
1.73
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,575,937 · 33 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
1w02w13w24w35w46w57w68w719w322w331w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x356d1c5e…5ec0
0xd32edf…ff58
15 touches
28 conflicts
0xc5847c4d…a65c
0x34b655…2a6f
12 touches
15 conflicts
0x5108e265…f5b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…001a
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
10 touches
10 conflicts
0x10c19272…7441
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
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
28 conflicts on slot 0x356d1c5e79…bd5ec0
Audit this contract →
← previous block·next block →recent activity