← previous blocknext block →recent activity
Analyzing
Block #101,062,970
24 transactions · 23 stateful · 2026-09-01 14:13:05 UTC
Parallelism
67/100
Blocked
61%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,062,970 · 24 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
1w02w13w24w35w47w48w39w410w411w518w619w520w723w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90c3ee22…6f78
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0xd25997d0…a683
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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
15 conflicts on slot 0x90c3ee22e8…136f78
Audit this contract →
← previous block·next block →recent activity