← previous blocknext block →recent activity
Analyzing
Block #108,496,261
30 transactions · 27 stateful · 2026-09-27 15:04:28 UTC
Parallelism
70/100
Blocked
52%
Avg conflicts / tx
1.33
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #108,496,261 · 30 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
1w02w13w24w35w46w57w610w317w724w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcab2e36c…61ed
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x3bd55803…5d4c
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
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
28 conflicts on slot 0xcab2e36c5e…8361ed
Audit this contract →
← previous block·next block →recent activity