← previous blocknext block →recent activity
Analyzing
Block #76,197,938
14 transactions · 11 stateful · 2026-05-22 05:28:32 UTC
Parallelism
79/100
Blocked
18%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,197,938 · 14 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
1w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x08a4fb1e…233d
0x065c9d…c394
2 touches
0 conflicts
0x13c19447…dc04
0x065c9d…c394
2 touches
0 conflicts
0x40e22841…435c
0x065c9d…c394
2 touches
0 conflicts
0x828339f8…c4ee
0x065c9d…c394
2 touches
0 conflicts
0xedf9d18f…8092
0x065c9d…c394
2 touches
0 conflicts
0xef83e215…a0c7
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