← previous blocknext block →recent activity
Analyzing
Block #106,030,470
23 transactions · 21 stateful · 2026-09-19 00:10:24 UTC
Parallelism
70/100
Blocked
52%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,030,470 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w08w19w010w117w218w319w520w622w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b687853…b6ce
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xd59f6ed1…03e7
0x1b6862…e19c
8 touches
6 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
10 conflicts on slot 0x7b68785305…52b6ce
Audit this contract →
← previous block·next block →recent activity