← previous blocknext block →recent activity
Analyzing
Block #108,678,338
102 transactions · 66 stateful · 2026-09-28 06:21:23 UTC
Parallelism
78/100
Blocked
80%
Avg conflicts / tx
2.59
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #108,678,338 · 102 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
1w03w04w115w118w221w224w525w627w729w831w733w341w1042w1146w1447w248w252w1279w880w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36a42dcf…104d
0xd32edf…ff58
29 touches
105 conflicts
0x00000000…0002
0x125f12…a50b
20 touches
45 conflicts
0xaad6be10…0801
0x2a68ba…90c5
16 touches
28 conflicts
0x00000000…0018
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0028
0x1b6862…e19c
14 touches
21 conflicts
0x6235638c…6436
0x1b6862…e19c
14 touches
21 conflicts
0xcb45d9d6…cb80
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
14 touches
21 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
105 conflicts on slot 0x36a42dcfd5…13104d
Audit this contract →
← previous block·next block →recent activity