← previous blocknext block →recent activity
Analyzing
Block #72,979,941
30 transactions · 20 stateful · 2026-05-07 07:31:00 UTC
Parallelism
80/100
Blocked
60%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #72,979,941 · 30 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
1w02w13w24w35w48w09w114w515w016w117w218w322w228w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x065463ba…8557
0xd32edf…ff58
11 touches
15 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xba5743c7…21c5
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x47c1a8e8…f74a
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ab
0x8d66a4…3095
5 touches
3 conflicts
0x0b390c61…dc07
0x065c9d…c394
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 0x065463bafa…908557
Audit this contract →
← previous block·next block →recent activity