← previous blocknext block →recent activity
Analyzing
Block #75,572,738
5 transactions · 4 stateful · 2026-05-19 08:01:22 UTC
Parallelism
60/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,572,738 · 5 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x01d531ea…d025
0x065c9d…c394
2 touches
0 conflicts
0x02f4bd10…c90e
0x065c9d…c394
2 touches
0 conflicts
0x17d89f4f…30c9
0x065c9d…c394
2 touches
0 conflicts
0x18b9bf34…31af
0x065c9d…c394
2 touches
0 conflicts
0x259b27ce…347d
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