← previous blocknext block →recent activity
Analyzing
Block #108,512,811
38 transactions · 36 stateful · 2026-09-27 16:27:48 UTC
Parallelism
76/100
Blocked
64%
Avg conflicts / tx
2.24
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #108,512,811 · 38 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36e16e03…ac2f
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x485d2778…aa5f
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd6ce21f1…e5cc
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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
36 conflicts on slot 0x36e16e03b3…25ac2f
Audit this contract →
← previous block·next block →recent activity