← previous blocknext block →recent activity
Analyzing
Block #76,441,354
13 transactions · 10 stateful · 2026-05-23 08:29:31 UTC
Parallelism
77/100
Blocked
20%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,441,354 · 13 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
1w05w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xb42171f3…ef8f
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x122c0d…e3fa
2 touches
0 conflicts
0x488a5ee6…541e
0x122c0d…e3fa
2 touches
0 conflicts
0x488a5ee6…541f
0x122c0d…e3fa
2 touches
0 conflicts
0x772a00e8…bc4a
0x122c0d…e3fa
2 touches
0 conflicts
0x8152da92…0d1c
0x122c0d…e3fa
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: MarginAccount
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity