← previous blocknext block →recent activity
Analyzing
Block #76,231,578
13 transactions · 10 stateful · 2026-05-22 09:12:51 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,231,578 · 13 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
2w03w14w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1ff6cb1…f865
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xbe7e7529…2c42
0x065c9d…c394
3 touches
1 conflict
0x49e349f6…7f78
0x065c9d…c394
2 touches
0 conflicts
0x794f2f95…5ae6
0x065c9d…c394
2 touches
0 conflicts
0x8bf16520…e12f
0x065c9d…c394
2 touches
0 conflicts
0xb4bd958b…7f76
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 0xd1ff6cb109…5ef865
Audit this contract →
← previous block·next block →recent activity