← previous blocknext block →recent activity
Analyzing
Block #108,476,915
35 transactions · 28 stateful · 2026-09-27 13:27:04 UTC
Parallelism
80/100
Blocked
54%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,476,915 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w322w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8ae77d3…f708
0xd32edf…ff58
13 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x7edc963c…7630
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x90d24713…b88c
0x1b6862…e19c
4 touches
1 conflict
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
21 conflicts on slot 0xe8ae77d39a…06f708
Audit this contract →
← previous block·next block →recent activity