← previous blocknext block →recent activity
Analyzing
Block #108,433,743
24 transactions · 19 stateful · 2026-09-27 09:49:45 UTC
Parallelism
67/100
Blocked
58%
Avg conflicts / tx
1.42
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,433,743 · 24 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
1w02w13w24w35w46w57w616w720w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ea3307d…6896
0xd32edf…ff58
15 touches
28 conflicts
0xd5b10148…e634
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001b
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002b
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 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 0x5ea3307d3d…5d6896
Audit this contract →
← previous block·next block →recent activity