← previous blocknext block →recent activity
Analyzing
Block #76,238,317
13 transactions · 11 stateful · 2026-05-22 09:57:44 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,238,317 · 13 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
3w04w05w18w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x03226734…d6d2
0xa6afd3…d132
4 touches
1 conflict
0x7b46425f…be23
0xa6afd3…d132
4 touches
1 conflict
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0x057ac2ab…400e
0x188d58…ea8e
2 touches
0 conflicts
0x057ac2ab…4010
0x188d58…ea8e
2 touches
0 conflicts
0x0f67f96d…f837
0x188d58…ea8e
2 touches
0 conflicts
0x14ba0e5f…a748
0x188d58…ea8e
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