← previous blocknext block →recent activity
Analyzing
Block #106,921,510
68 transactions · 53 stateful · 2026-09-22 02:56:00 UTC
Parallelism
68/100
Blocked
77%
Avg conflicts / tx
3.38
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #106,921,510 · 68 txs across 22 waves · depth 22
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
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w49w512w217w318w419w520w621w722w823w924w1036w651w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf82fef6a…2553
0xd32edf…ff58
23 touches
66 conflicts
0xca841faa…486a
0x34b655…2a6f
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0012
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…001d
0x1b6862…e19c
18 touches
36 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…003d
0x065c9d…c394
16 touches
28 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
66 conflicts on slot 0xf82fef6a2b…c02553
Audit this contract →
← previous block·next block →recent activity