← previous blocknext block →recent activity
Analyzing
Block #100,440,264
23 transactions · 21 stateful · 2026-08-30 10:00:02 UTC
Parallelism
74/100
Blocked
48%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,440,264 · 23 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
1w02w13w24w37w08w112w413w515w217w218w322w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cf9998f…c4ed
0xd32edf…ff58
11 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xea0e5cfa…7085
0x34b655…2a6f
6 touches
3 conflicts
0x8db32935…81a7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x93afca4c…b47b
0x1b6862…e19c
4 touches
1 conflict
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 0x0cf9998f5a…f7c4ed
Audit this contract →
← previous block·next block →recent activity