← previous blocknext block →recent activity
Analyzing
Block #76,447,034
12 transactions · 10 stateful · 2026-05-23 09:07:16 UTC
Parallelism
75/100
Blocked
30%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,447,034 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x8bc3e255…0a0b
0xa6afd3…d132
6 touches
3 conflicts
0xcc7ea25c…8301
0x065c9d…c394
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x0bd261be…21c6
0xa6afd3…d132
4 touches
1 conflict
0xc113e590…1fcb
0x065c9d…c394
3 touches
1 conflict
0x1a1a4324…9301
0x065c9d…c394
3 touches
1 conflict
0x3238af5e…31f6
0x065c9d…c394
2 touches
0 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: Kuru Exchange: Market-WETH/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity