← previous blocknext block →recent activity
Analyzing
Block #108,962,140
18 transactions · 15 stateful · 2026-09-29 06:14:11 UTC
Parallelism
44/100
Blocked
67%
Avg conflicts / tx
2.11
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,962,140 · 18 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
1w02w13w24w35w46w57w69w712w817w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43fa1535…8ae4
0xd32edf…ff58
17 touches
36 conflicts
0x1b322c91…560a
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001e
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002e
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0040
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0057
0x1b6862…e19c
16 touches
28 conflicts
0x784d7a94…94a1
0x1b6862…e19c
16 touches
28 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
36 conflicts on slot 0x43fa153524…648ae4
Audit this contract →
← previous block·next block →recent activity