← previous blocknext block →recent activity
Analyzing
Block #101,018,808
20 transactions · 18 stateful · 2026-09-01 10:30:54 UTC
Parallelism
65/100
Blocked
67%
Avg conflicts / tx
1.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,018,808 · 20 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
1w02w13w24w36w08w011w112w213w414w115w516w217w318w419w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ef2f418…5c8c
0xd32edf…ff58
13 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd5b10148…e638
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 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 0x1ef2f41887…3a5c8c
Audit this contract →
← previous block·next block →recent activity