← previous blocknext block →recent activity
Analyzing
Block #71,043,976
27 transactions · 20 stateful · 2026-04-28 08:25:35 UTC
Parallelism
81/100
Blocked
55%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #71,043,976 · 27 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
1w02w13w24w311w013w116w017w019w120w221w122w223w325w126w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7aacf6d…c441
0xd32edf…ff58
9 touches
10 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xffe431af…8faa
0x131a2e…0da9
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…001f
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 0xf7aacf6d2f…eac441
Audit this contract →
← previous block·next block →recent activity