← previous blocknext block →recent activity
Analyzing
Block #108,965,434
54 transactions · 49 stateful · 2026-09-29 06:30:53 UTC
Parallelism
56/100
Blocked
78%
Avg conflicts / tx
4.39
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #108,965,434 · 54 txs across 24 waves · depth 24
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1318w1420w123w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6a249d5…8950
0xd32edf…ff58
31 touches
120 conflicts
0x00000000…0015
0x1b6862…e19c
30 touches
105 conflicts
0x17a7f697…dcb7
0x1b6862…e19c
30 touches
105 conflicts
0x00000000…0013
0x1b6862…e19c
30 touches
105 conflicts
0x00000000…0012
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0057
0x1b6862…e19c
24 touches
66 conflicts
0x57d3b231…a412
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…002e
0x1b6862…e19c
24 touches
66 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
120 conflicts on slot 0xd6a249d5aa…6f8950
Audit this contract →
← previous block·next block →recent activity