← previous blocknext block →recent activity
Analyzing
Block #107,817,276
18 transactions · 17 stateful · 2026-09-25 06:07:10 UTC
Parallelism
67/100
Blocked
59%
Avg conflicts / tx
1.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,817,276 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w09w212w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0e8cb7e…451e
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x9b334941…fde1
0x1b6862…e19c
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xc7679110…572d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x125f12…a50b
4 touches
1 conflict
0x00000000…0009
0x125f12…a50b
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
15 conflicts on slot 0xf0e8cb7e5d…e6451e
Audit this contract →
← previous block·next block →recent activity