← previous blocknext block →recent activity
Analyzing
Block #76,444,253
30 transactions · 22 stateful · 2026-05-23 08:48:43 UTC
Parallelism
77/100
Blocked
64%
Avg conflicts / tx
1.07
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,444,253 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w410w111w112w113w216w518w125w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c2f6fc1…a18f
0xd32edf…ff58
11 touches
15 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0x8c511218…5cad
0x065c9d…c394
6 touches
3 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
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
15 conflicts on slot 0x2c2f6fc116…f2a18f
Audit this contract →
← previous block·next block →recent activity