← previous blocknext block →recent activity
Analyzing
Block #106,328,109
37 transactions · 24 stateful · 2026-09-20 01:08:22 UTC
Parallelism
65/100
Blocked
71%
Avg conflicts / tx
2.05
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,328,109 · 37 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1126w127w133w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33e5f630…36b4
0xd32edf…ff58
23 touches
66 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0019
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0029
0x1b6862…e19c
16 touches
28 conflicts
0x84611dd3…b342
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
66 conflicts on slot 0x33e5f630d5…8b36b4
Audit this contract →
← previous block·next block →recent activity