← previous blocknext block →recent activity
Analyzing
Block #75,941,143
13 transactions · 10 stateful · 2026-05-21 00:57:55 UTC
Parallelism
77/100
Blocked
20%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,941,143 · 13 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
3w06w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x4d5920c0…0a5f
0xd32edf…ff58
3 touches
1 conflict
0x0b34c659…c31e
0x065c9d…c394
2 touches
0 conflicts
0x0db0e231…e03b
0x065c9d…c394
2 touches
0 conflicts
0x59b0fac8…f933
0x065c9d…c394
2 touches
0 conflicts
0x9249c39e…79a9
0x065c9d…c394
2 touches
0 conflicts
0x0a809ce1…7894
0x34b655…2a6f
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