← previous blocknext block →recent activity
Analyzing
Block #76,042,597
9 transactions · 7 stateful · 2026-05-21 12:13:23 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,042,597 · 9 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4a91875f…4d83
0x065c9d…c394
3 touches
1 conflict
0xd75c74bb…469b
0x065c9d…c394
3 touches
1 conflict
0x06f2b25a…f6b5
0x065c9d…c394
2 touches
0 conflicts
0x266367f8…8bbd
0x065c9d…c394
2 touches
0 conflicts
0x455f7c50…0a40
0x065c9d…c394
2 touches
0 conflicts
0x5b6a7a6f…64e7
0x065c9d…c394
2 touches
0 conflicts
0x88a68e08…ff61
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity