← previous blocknext block →recent activity
Analyzing
Block #71,046,011
25 transactions · 22 stateful · 2026-04-28 08:39:09 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.92
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #71,046,011 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w410w511w612w713w814w917w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfadc1d5a…0fd4
0xd32edf…ff58
19 touches
45 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
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
45 conflicts on slot 0xfadc1d5aa1…7a0fd4
Audit this contract →
← previous block·next block →recent activity