← previous blocknext block →recent activity
Analyzing
Block #76,559,481
24 transactions · 20 stateful · 2026-05-23 21:36:10 UTC
Parallelism
83/100
Blocked
55%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,559,481 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w16w211w313w215w316w318w019w120w322w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f7f678b…545e
0xd32edf…ff58
7 touches
6 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
6 touches
3 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
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 0x0f7f678b5d…f3545e
Audit this contract →
← previous block·next block →recent activity