← previous blocknext block →recent activity
Analyzing
Block #100,984,322
39 transactions · 35 stateful · 2026-09-01 07:37:20 UTC
Parallelism
85/100
Blocked
51%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,984,322 · 39 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
1w02w13w05w18w212w313w016w219w321w022w123w227w428w329w138w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x466edc01…d300
0xd32edf…ff58
11 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x93589259…6c10
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0x466edc01d0…f2d300
Audit this contract →
← previous block·next block →recent activity