← previous blocknext block →recent activity
Analyzing
Block #106,187,516
25 transactions · 23 stateful · 2026-09-19 13:20:45 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,187,516 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w49w010w111w212w013w114w216w319w020w121w022w123w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eeeb9bf…04c8
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x11998eac…f9a5
0x1b6862…e19c
6 touches
3 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
6 conflicts on slot 0x0eeeb9bf69…9004c8
Audit this contract →
← previous block·next block →recent activity