← previous blocknext block →recent activity
Analyzing
Block #102,551,416
28 transactions · 21 stateful · 2026-09-06 19:26:33 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.21
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,551,416 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w27w38w49w512w614w719w225w627w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd371c451…8015
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0x580c6fe7…0fe7
0x1b6862…e19c
10 touches
10 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
21 conflicts on slot 0xd371c45160…6d8015
Audit this contract →
← previous block·next block →recent activity