← previous blocknext block →recent activity
Analyzing
Block #106,031,199
28 transactions · 27 stateful · 2026-09-19 00:14:05 UTC
Parallelism
86/100
Blocked
37%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,031,199 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w07w18w113w214w215w222w024w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0e9fe18…2d11
0xd32edf…ff58
7 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x110a3804…f842
0x34b655…2a6f
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x7dd96c96…7335
0x34b655…2a6f
4 touches
1 conflict
0x839d77a9…9a51
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xe0e9fe18a5…9f2d11
Audit this contract →
← previous block·next block →recent activity