← previous blocknext block →recent activity
Analyzing
Block #76,033,902
15 transactions · 14 stateful · 2026-05-21 11:15:31 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,033,902 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w17w29w210w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
8 touches
6 conflicts
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x33018431…8f5c
0x188d58…ea8e
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x31db677c…366a
0x065c9d…c394
4 touches
1 conflict
0x33018431…8f5e
0x188d58…ea8e
4 touches
1 conflict
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity