← previous blocknext block →recent activity
Analyzing
Block #75,607,070
6 transactions · 5 stateful · 2026-05-19 11:50:42 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,607,070 · 6 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x33969c54…2a37
0x065c9d…c394
4 touches
1 conflict
0x062cbb5d…35d3
0x065c9d…c394
2 touches
0 conflicts
0x26bb5586…80dd
0x065c9d…c394
2 touches
0 conflicts
0x4eb3fd45…4d6e
0x065c9d…c394
2 touches
0 conflicts
0x5aa5abc5…a190
0x065c9d…c394
2 touches
0 conflicts
0x892daf6e…48d8
0x065c9d…c394
2 touches
0 conflicts
0xe40d3108…7973
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