← previous blocknext block →recent activity
Analyzing
Block #106,282,310
14 transactions · 10 stateful · 2026-09-19 21:17:55 UTC
Parallelism
79/100
Blocked
40%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,282,310 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w211w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36e00d5b…c803
0xd32edf…ff58
5 touches
3 conflicts
0x59658b83…2225
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xddd20e39…d524
0x34b655…2a6f
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
3 conflicts on slot 0x36e00d5be2…3ac803
Audit this contract →
← previous block·next block →recent activity