← previous blocknext block →recent activity
Analyzing
Block #107,612,489
25 transactions · 23 stateful · 2026-09-24 12:54:37 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
1.04
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,612,489 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w512w613w715w016w117w218w324w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5613c011…5e47
0xd32edf…ff58
11 touches
15 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
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 0x5613c01105…a95e47
Audit this contract →
← previous block·next block →recent activity