← previous blocknext block →recent activity
Analyzing
Block #75,701,840
14 transactions · 9 stateful · 2026-05-19 22:22:56 UTC
Parallelism
86/100
Blocked
11%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,701,840 · 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
5w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x331eb687…067d
0x065c9d…c394
2 touches
0 conflicts
0x443d196a…3ce1
0x065c9d…c394
2 touches
0 conflicts
0x69a3dbbe…749f
0x065c9d…c394
2 touches
0 conflicts
0xd40ecabc…c618
0x065c9d…c394
2 touches
0 conflicts
0xfeacb9f5…e0f9
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xcc4f1f1446…7caa5f
Audit this contract →
← previous block·next block →recent activity