← previous blocknext block →recent activity
Analyzing
Block #101,020,444
22 transactions · 20 stateful · 2026-09-01 10:39:07 UTC
Parallelism
64/100
Blocked
60%
Avg conflicts / tx
1.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,020,444 · 22 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
1w02w13w24w35w411w413w516w619w720w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04f78630…68e4
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x9ac040c1…8226
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x5f77d607…2c84
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
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
21 conflicts on slot 0x04f78630a4…fd68e4
Audit this contract →
← previous block·next block →recent activity