← previous blocknext block →recent activity
Analyzing
Block #71,042,862
29 transactions · 23 stateful · 2026-04-28 08:18:10 UTC
Parallelism
72/100
Blocked
43%
Avg conflicts / tx
1.07
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #71,042,862 · 29 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w47w513w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0617f54…23df
0xd32edf…ff58
15 touches
28 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0xd025d7d7…f05a
0x3bd359…433a
4 touches
1 conflict
0x548c90b5…acbd
0x5afd3e…7620
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x6aa624fd…a852
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0xf233a094…d090
0x065c9d…c394
3 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
28 conflicts on slot 0xb0617f54b2…7a23df
Audit this contract →
← previous block·next block →recent activity