← previous blocknext block →recent activity
Analyzing
Block #76,211,757
14 transactions · 12 stateful · 2026-05-22 07:00:21 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,211,757 · 14 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
1w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x2545c9e0…e69b
0x065c9d…c394
3 touches
1 conflict
0x4a162cc1…6ca2
0x065c9d…c394
3 touches
1 conflict
0x3e23b56f…bb78
0x065c9d…c394
2 touches
0 conflicts
0x56bd6ab0…6499
0x065c9d…c394
2 touches
0 conflicts
0x9546af52…0a6d
0x065c9d…c394
2 touches
0 conflicts
0xda37f424…02d9
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