← previous blocknext block →recent activity
Analyzing
Block #76,340,360
11 transactions · 10 stateful · 2026-05-22 21:16:46 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,340,360 · 11 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
2w03w05w16w27w18w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xd71a331e…42ea
0xa6afd3…d132
6 touches
3 conflicts
0xc51d3663…0f45
0xa6afd3…d132
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0x3484c9df…bfd5
0x1d1325…2305
2 touches
0 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
2 touches
0 conflicts
0x12a9b76e…cb76
0x3bd359…433a
2 touches
0 conflicts
0x44ed742f…63f5
0x3bd359…433a
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