← previous blocknext block →recent activity
Analyzing
Block #71,289,767
16 transactions · 13 stateful · 2026-04-29 11:41:51 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #71,289,767 · 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
1w02w14w29w310w414w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19668311…d7e5
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0000
0x8fd63a…536c
4 touches
1 conflict
0x00000000…0001
0x8fd63a…536c
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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
6 conflicts on slot 0x196683110d…35d7e5
Audit this contract →
← previous block·next block →recent activity