← previous blocknext block →recent activity
Analyzing
Block #106,425,833
34 transactions · 33 stateful · 2026-09-20 09:20:11 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
2.09
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,425,833 · 34 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w311w412w513w614w715w816w920w1021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46ee3415…5dbe
0xd32edf…ff58
21 touches
55 conflicts
0x00000000…0012
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…001b
0x1b6862…e19c
18 touches
36 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
18 touches
36 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
18 touches
36 conflicts
0xb6ed530c…d450
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 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
55 conflicts on slot 0x46ee3415cf…ce5dbe
Audit this contract →
← previous block·next block →recent activity