← previous blocknext block →recent activity
Analyzing
Block #102,212,725
35 transactions · 32 stateful · 2026-09-05 14:50:13 UTC
Parallelism
74/100
Blocked
63%
Avg conflicts / tx
1.57
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #102,212,725 · 35 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w310w411w512w621w723w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ac96780…7e38
0xd32edf…ff58
15 touches
28 conflicts
0xa952c504…7b64
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xd5b10148…e638
0x1b6862…e19c
8 touches
6 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
28 conflicts on slot 0x4ac967800b…0d7e38
Audit this contract →
← previous block·next block →recent activity