← previous blocknext block →recent activity
Analyzing
Block #101,015,934
37 transactions · 28 stateful · 2026-09-01 10:16:26 UTC
Parallelism
81/100
Blocked
54%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,015,934 · 37 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w111w214w325w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5bc5b1d0…c50e
0xd32edf…ff58
13 touches
21 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xc813cd99…532b
0x065c9d…c394
4 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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
21 conflicts on slot 0x5bc5b1d02f…54c50e
Audit this contract →
← previous block·next block →recent activity