← previous blocknext block →recent activity
Analyzing
Block #108,285,863
22 transactions · 21 stateful · 2026-09-26 21:25:34 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,285,863 · 22 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
1w03w14w05w06w111w116w218w319w020w121w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d4a5015…8fc5
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb80
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xaa273a8e…7133
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
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 0x4d4a501528…868fc5
Audit this contract →
← previous block·next block →recent activity