← previous blocknext block →recent activity
Analyzing
Block #76,239,064
13 transactions · 11 stateful · 2026-05-22 10:02:44 UTC
Parallelism
77/100
Blocked
18%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,239,064 · 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
2w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x10a56d9d…02e4
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2c4f30a9…b162
0x065c9d…c394
2 touches
0 conflicts
0x2e87cee5…8b04
0x065c9d…c394
2 touches
0 conflicts
0x5e343b6a…09a4
0x065c9d…c394
2 touches
0 conflicts
0x5f68914e…1aa3
0x065c9d…c394
2 touches
0 conflicts
0x6b5f9db7…4bda
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-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity