← previous blocknext block →recent activity
Analyzing
Block #76,239,407
9 transactions · 9 stateful · 2026-05-22 10:05:00 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,239,407 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x03226734…d6d2
0xa6afd3…d132
4 touches
1 conflict
0x27e56714…14ef
0x065c9d…c394
2 touches
0 conflicts
0x5a55e68c…47ad
0x065c9d…c394
2 touches
0 conflicts
0x7a8b611c…af22
0x065c9d…c394
2 touches
0 conflicts
0x7b8ae145…4cae
0x065c9d…c394
2 touches
0 conflicts
0xa9a29234…6efd
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity