← previous blocknext block →recent activity
Analyzing
Block #101,149,375
23 transactions · 22 stateful · 2026-09-01 21:28:05 UTC
Parallelism
65/100
Blocked
64%
Avg conflicts / tx
1.61
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,149,375 · 23 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
1w02w13w24w39w212w413w514w619w320w722w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3d45a2f…33b7
0xd32edf…ff58
15 touches
28 conflicts
0xd53220ed…4735
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0019
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 0xa3d45a2fb6…8a33b7
Audit this contract →
← previous block·next block →recent activity