← previous blocknext block →recent activity
Analyzing
Block #108,619,607
69 transactions · 60 stateful · 2026-09-28 01:25:36 UTC
Parallelism
70/100
Blocked
80%
Avg conflicts / tx
2.94
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #108,619,607 · 69 txs across 21 waves · depth 21
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w17w28w39w410w512w614w716w318w125w227w244w848w949w1050w1051w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f1c1773…537b
0xd32edf…ff58
27 touches
91 conflicts
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0xaad6be10…0801
0x2a68ba…90c5
14 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xf3d7a307…4d63
0x065c9d…c394
12 touches
15 conflicts
0x00000000…0002
0x125f12…a50b
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
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
91 conflicts on slot 0x1f1c177304…c2537b
Audit this contract →
← previous block·next block →recent activity