← previous blocknext block →recent activity
Analyzing
Block #106,242,638
25 transactions · 24 stateful · 2026-09-19 17:58:16 UTC
Parallelism
72/100
Blocked
63%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,242,638 · 25 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
1w02w13w24w35w46w57w38w510w011w113w414w523w224w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50f7d5c8…03ff
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x839c0c71…bada
0x34b655…2a6f
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…002f
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
15 conflicts on slot 0x50f7d5c8aa…2503ff
Audit this contract →
← previous block·next block →recent activity