← previous blocknext block →recent activity
Analyzing
Block #76,193,427
10 transactions · 8 stateful · 2026-05-22 04:58:33 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,193,427 · 10 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9657ab1…8737
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5bf1870d…2fcb
0x065c9d…c394
3 touches
1 conflict
0x4e646b92…5169
0x065c9d…c394
3 touches
1 conflict
0x49bc8810…08ef
0x065c9d…c394
2 touches
0 conflicts
0x502337fc…a92d
0x065c9d…c394
2 touches
0 conflicts
0x7880a631…7b73
0x065c9d…c394
2 touches
0 conflicts
0xf04317dd…79e0
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 0xc9657ab1c6…f78737
Audit this contract →
← previous block·next block →recent activity