← previous blocknext block →recent activity
Analyzing
Block #101,088,322
28 transactions · 23 stateful · 2026-09-01 16:20:57 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
1.18
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #101,088,322 · 28 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
2w04w15w26w37w48w59w610w713w817w626w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d378a09…3e74
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x17a7f697…dcb1
0x1b6862…e19c
12 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0018
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0028
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 0x5d378a09f7…273e74
Audit this contract →
← previous block·next block →recent activity