← previous blocknext block →recent activity
Analyzing
Block #76,142,231
10 transactions · 10 stateful · 2026-05-21 23:17:37 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,142,231 · 10 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
2w04w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x050728ba…6f71
0x065c9d…c394
4 touches
1 conflict
0xafb347e8…1e11
0x065c9d…c394
3 touches
1 conflict
0x5c219243…3abe
0x065c9d…c394
3 touches
1 conflict
0xe43a949d…630d
0x065c9d…c394
2 touches
0 conflicts
0xef185ccd…9a44
0x065c9d…c394
2 touches
0 conflicts
0x729c91b8…9537
0x188d58…ea8e
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