← previous blocknext block →recent activity
Analyzing
Block #75,525,584
10 transactions · 5 stateful · 2026-05-19 02:47:48 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,525,584 · 10 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
0xeef33e6f…a093
0x065c9d…c394
3 touches
1 conflict
0x36f3a6f0…ade1
0x065c9d…c394
3 touches
1 conflict
0x021f8b15…0789
0x065c9d…c394
2 touches
0 conflicts
0x695dc4d4…346c
0x065c9d…c394
2 touches
0 conflicts
0x7638c2dc…f6a7
0x065c9d…c394
2 touches
0 conflicts
0x892daf6e…48d8
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x1d1325…2305
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