← previous blocknext block →recent activity
Analyzing
Block #76,306,372
18 transactions · 11 stateful · 2026-05-22 17:30:30 UTC
Parallelism
89/100
Blocked
27%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,306,372 · 18 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
1w02w09w110w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7437d0e6…ceb9
0x065c9d…c394
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3a6e7600…e1f1
0xa6afd3…d132
4 touches
1 conflict
0x10d80fee…dbda
0x1d1325…2305
2 touches
0 conflicts
0x2f4b2cf9…4e1e
0x1d1325…2305
2 touches
0 conflicts
0x7aa91b8f…d070
0x1d1325…2305
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity