← previous blocknext block →recent activity
Analyzing
Block #71,342,440
9 transactions · 8 stateful · 2026-04-29 17:33:00 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,342,440 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc38e0db9…d367
0xd32edf…ff58
5 touches
3 conflicts
0xc824469a…641c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x20a828dc…3b59
0x065c9d…c394
2 touches
0 conflicts
0x529e56a8…3550
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 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
3 conflicts on slot 0xc38e0db94f…01d367
Audit this contract →
← previous block·next block →recent activity