← previous blocknext block →recent activity
Analyzing
Block #102,359,448
17 transactions · 16 stateful · 2026-09-06 03:13:37 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,359,448 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w09w112w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f261638…9ea7
0xd32edf…ff58
5 touches
3 conflicts
0x5a3732cb…edae
0x1b6862…e19c
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfb682e7d…dde9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
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 0x6f261638f1…f29ea7
Audit this contract →
← previous block·next block →recent activity