← previous blocknext block →recent activity
Analyzing
Block #76,229,614
13 transactions · 11 stateful · 2026-05-22 08:59:44 UTC
Parallelism
62/100
Blocked
36%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,229,614 · 13 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
1w02w14w25w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xf282c2b3…28b4
0xa6afd3…d132
6 touches
3 conflicts
0x03226734…d6d2
0xa6afd3…d132
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x14cbac29…2179
0x065c9d…c394
2 touches
0 conflicts
0x2862b2f1…08b0
0x065c9d…c394
2 touches
0 conflicts
0x377a0fb5…0ea7
0x065c9d…c394
2 touches
0 conflicts
0xab47a909…7ac8
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity