← previous blocknext block →recent activity
Analyzing
Block #75,106,358
9 transactions · 7 stateful · 2026-05-17 03:58:10 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,106,358 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xab500414…98c8
0x065c9d…c394
3 touches
1 conflict
0xf1c0c892…aae0
0x065c9d…c394
3 touches
1 conflict
0x43427436…baca
0x065c9d…c394
2 touches
0 conflicts
0x59fd8b5a…590f
0x065c9d…c394
2 touches
0 conflicts
0x6c215fb1…481a
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 0xba38536db1…342b7d
Audit this contract →
← previous block·next block →recent activity