← previous blocknext block →recent activity
Analyzing
Block #76,212,752
9 transactions · 6 stateful · 2026-05-22 07:07:03 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,212,752 · 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
1w02w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x279e658f…de3d
0x96b79e…d00a
4 touches
1 conflict
0x6481c337…49f5
0x065c9d…c394
3 touches
1 conflict
0x1026b816…2901
0x065c9d…c394
3 touches
1 conflict
0x302d24fe…fc3d
0x065c9d…c394
2 touches
0 conflicts
0x435600db…23be
0x065c9d…c394
2 touches
0 conflicts
0x77d23415…388f
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