← previous blocknext block →recent activity
Analyzing
Block #108,619,496
72 transactions · 58 stateful · 2026-09-28 01:25:02 UTC
Parallelism
74/100
Blocked
76%
Avg conflicts / tx
3.32
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #108,619,496 · 72 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w18w09w112w213w121w222w326w427w531w439w740w841w842w943w1044w1145w1246w147w1349w1450w1552w1654w1757w265w367w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd31be0fa…afad
0xd32edf…ff58
33 touches
136 conflicts
0x00000000…0013
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0x03f9cc30…b46c
0x1b6862…e19c
18 touches
36 conflicts
0xaad6be10…0801
0x2a68ba…90c5
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001f
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002f
0x1b6862…e19c
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
136 conflicts on slot 0xd31be0fa43…bdafad
Audit this contract →
← previous block·next block →recent activity