← previous blocknext block →recent activity
Analyzing
Block #101,314,261
27 transactions · 24 stateful · 2026-09-02 11:17:37 UTC
Parallelism
78/100
Blocked
42%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,314,261 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w47w412w015w116w418w519w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28a20d95…9600
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x4979282b…2936
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xa36257f6…048b
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
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 0x28a20d95f1…fb9600
Audit this contract →
← previous block·next block →recent activity