← previous blocknext block →recent activity
Analyzing
Block #101,303,442
27 transactions · 23 stateful · 2026-09-02 10:23:11 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
1.04
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,303,442 · 27 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
1w02w13w24w36w49w212w013w116w523w024w325w626w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e2e56e0…d005
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…001c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xd25997d0…a687
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
15 conflicts on slot 0x3e2e56e06e…e4d005
Audit this contract →
← previous block·next block →recent activity