← previous blocknext block →recent activity
Analyzing
Block #108,495,905
19 transactions · 17 stateful · 2026-09-27 15:02:41 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,495,905 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w17w18w29w315w216w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6d678dd…ec37
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x125f12…a50b
4 touches
1 conflict
0x00000000…0009
0x125f12…a50b
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
10 conflicts on slot 0xc6d678dd40…a5ec37
Audit this contract →
← previous block·next block →recent activity