← previous blocknext block →recent activity
Analyzing
Block #101,300,720
35 transactions · 30 stateful · 2026-09-02 10:09:29 UTC
Parallelism
77/100
Blocked
57%
Avg conflicts / tx
1.46
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,300,720 · 35 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
1w02w13w24w35w38w411w113w220w521w423w525w626w427w534w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5743a7d…f353
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
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
28 conflicts on slot 0xc5743a7dd8…cbf353
Audit this contract →
← previous block·next block →recent activity