← previous blocknext block →recent activity
Analyzing
Block #76,195,432
9 transactions · 9 stateful · 2026-05-22 05:11:54 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,195,432 · 9 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe2bac2b…2cec
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1e0da364…115f
0x065c9d…c394
2 touches
0 conflicts
0x4ff0b310…5e4c
0x065c9d…c394
2 touches
0 conflicts
0x76733a19…f819
0x065c9d…c394
2 touches
0 conflicts
0xdc4a3cfd…25fc
0x065c9d…c394
2 touches
0 conflicts
0xe8337797…ba8e
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 0xfe2bac2b2f…482cec
Audit this contract →
← previous block·next block →recent activity