← previous blocknext block →recent activity
Analyzing
Block #75,107,055
7 transactions · 5 stateful · 2026-05-17 04:02:49 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,107,055 · 7 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
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x36dcf7f4…c37b
0x065c9d…c394
2 touches
0 conflicts
0x4145d7be…3406
0x065c9d…c394
2 touches
0 conflicts
0x526cb05f…8e7d
0x065c9d…c394
2 touches
0 conflicts
0x57269566…e38e
0x065c9d…c394
2 touches
0 conflicts
0x938a9978…d75a
0x065c9d…c394
2 touches
0 conflicts
0x9a47e98e…968e
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