← previous blocknext block →recent activity
Analyzing
Block #71,283,713
16 transactions · 12 stateful · 2026-04-29 11:01:36 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #71,283,713 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f33003b…5ce3
0xd32edf…ff58
9 touches
10 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0x69017fce…85bf
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
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
10 conflicts on slot 0x4f33003ba1…835ce3
Audit this contract →
← previous block·next block →recent activity