← previous blocknext block →recent activity
Analyzing
Block #108,671,606
23 transactions · 21 stateful · 2026-09-28 05:47:29 UTC
Parallelism
65/100
Blocked
48%
Avg conflicts / tx
1.09
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,671,606 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w511w513w614w718w222w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fef0c3c…428e
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0051
0x1b6862…e19c
8 touches
6 conflicts
0x5c421c70…c2eb
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
15 conflicts on slot 0x5fef0c3cbc…f4428e
Audit this contract →
← previous block·next block →recent activity