← previous blocknext block →recent activity
Analyzing
Block #108,603,537
64 transactions · 58 stateful · 2026-09-28 00:04:40 UTC
Parallelism
58/100
Blocked
88%
Avg conflicts / tx
4.83
Longest chain
27 deep
Execution timeline
did this block parallelize well?
view
block #108,603,537 · 64 txs across 27 waves · depth 27
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
wave w22
wave w23
wave w24
wave w25
wave w26
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w431w835w1341w1543w1746w2047w21
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd356b2a…4a01
0xd32edf…ff58
29 touches
105 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0x482471ad…122f
0x34b655…2a6f
22 touches
55 conflicts
0x42102e63…8aaa
0x1b6862…e19c
22 touches
55 conflicts
0x00000000…0013
0x1b6862…e19c
22 touches
55 conflicts
0x00000000…0015
0x1b6862…e19c
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0xca841faa…486a
0x34b655…2a6f
18 touches
36 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 0xfd356b2aa4…8d4a01
Audit this contract →
← previous block·next block →recent activity