← previous blocknext block →recent activity
Analyzing
Block #76,243,304
14 transactions · 12 stateful · 2026-05-22 10:30:55 UTC
Parallelism
71/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,243,304 · 14 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
1w02w16w07w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03226734…d6d2
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x76e96198…eec4
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0f7cf404…7558
0xa6afd3…d132
3 touches
1 conflict
0x00000000…000c
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…000e
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…000f
0x2b37ef…0bdc
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
1 conflict on slot 0x03226734aa…71d6d2
Audit this contract →
← previous block·next block →recent activity