← previous blocknext block →recent activity
Analyzing
Block #108,940,264
10 transactions · 10 stateful · 2026-09-29 04:23:23 UTC
Parallelism
30/100
Blocked
70%
Avg conflicts / tx
2.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,940,264 · 10 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
1w02w13w24w35w46w57w69w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06c5ff16…e913
0xd32edf…ff58
13 touches
21 conflicts
0xdb95e18e…c73c
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0040
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0056
0x1b6862…e19c
10 touches
10 conflicts
0x37d0a8fa…b67b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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 0x06c5ff1668…e4e913
Audit this contract →
← previous block·next block →recent activity