← previous blocknext block →recent activity
Analyzing
Block #76,141,237
10 transactions · 10 stateful · 2026-05-21 23:11:00 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,141,237 · 10 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
1w02w14w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0xc0593b19…9bab
0xd32edf…ff58
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x4ff6bd1c…73b9
0x065c9d…c394
2 touches
0 conflicts
0x500c6a86…83bb
0x065c9d…c394
2 touches
0 conflicts
0xb692909f…3de2
0x065c9d…c394
2 touches
0 conflicts
0xbbfa4c66…66d9
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 0x4175529119…79977f
Audit this contract →
← previous block·next block →recent activity