← previous blocknext block →recent activity
Analyzing
Block #108,276,178
18 transactions · 16 stateful · 2026-09-26 20:36:49 UTC
Parallelism
61/100
Blocked
56%
Avg conflicts / tx
1.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,276,178 · 18 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
1w02w13w24w35w46w57w08w111w617w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc778b1c1…61b6
0xd32edf…ff58
13 touches
21 conflicts
0xba5743c7…21bf
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x9aa49c1c…5bc4
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 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
21 conflicts on slot 0xc778b1c159…a761b6
Audit this contract →
← previous block·next block →recent activity