← previous blocknext block →recent activity
Analyzing
Block #108,366,998
12 transactions · 12 stateful · 2026-09-27 04:13:51 UTC
Parallelism
42/100
Blocked
58%
Avg conflicts / tx
1.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,366,998 · 12 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
1w02w13w24w35w46w57w610w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02e1b69f…6458
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xb89c7e78…0bee
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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 0x02e1b69f17…1e6458
Audit this contract →
← previous block·next block →recent activity