← previous blocknext block →recent activity
Analyzing
Block #106,028,610
38 transactions · 31 stateful · 2026-09-19 00:01:03 UTC
Parallelism
68/100
Blocked
65%
Avg conflicts / tx
1.71
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,028,610 · 38 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w713w822w626w927w1028w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x905f4826…d18d
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001b
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002b
0x1b6862…e19c
12 touches
15 conflicts
0x3e04662b…0da4
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
36 conflicts on slot 0x905f48269f…e6d18d
Audit this contract →
← previous block·next block →recent activity