← previous blocknext block →recent activity
Analyzing
Block #108,377,594
8 transactions · 8 stateful · 2026-09-27 05:07:10 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,377,594 · 8 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66ab9c88…3570
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x6940ae48…0c29
0x34b655…2a6f
6 touches
3 conflicts
0x872e51c8…ae27
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
6 touches
3 conflicts
0x40d6d1e9…131e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
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
6 conflicts on slot 0x66ab9c8809…ad3570
Audit this contract →
← previous block·next block →recent activity