← previous blocknext block →recent activity
Analyzing
Block #107,785,143
25 transactions · 24 stateful · 2026-09-25 03:25:19 UTC
Parallelism
64/100
Blocked
79%
Avg conflicts / tx
2.4
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #107,785,143 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w718w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb00df060…916e
0xd32edf…ff58
17 touches
36 conflicts
0x002fed35…79fa
0x2a68ba…90c5
12 touches
15 conflicts
0x4461ca16…3b5a
0x851145…3f07
11 touches
15 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0xd59f6ed1…03ea
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
36 conflicts on slot 0xb00df060eb…33916e
Audit this contract →
← previous block·next block →recent activity