← previous blocknext block →recent activity
Analyzing
Block #75,078,960
9 transactions · 8 stateful · 2026-05-17 00:55:15 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,078,960 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2930103b…5f35
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x324a14fb…0e23
0x065c9d…c394
2 touches
0 conflicts
0x4a8e4949…08c3
0x065c9d…c394
2 touches
0 conflicts
0x6dff7821…6df5
0x065c9d…c394
2 touches
0 conflicts
0x7730fb46…ce2f
0x065c9d…c394
2 touches
0 conflicts
0xcaa8c746…33c2
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 0x2930103bdd…c55f35
Audit this contract →
← previous block·next block →recent activity