← previous blocknext block →recent activity
Analyzing
Block #75,847,991
10 transactions · 8 stateful · 2026-05-20 14:37:15 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,847,991 · 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
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x1a0ba67e…1670
0x065c9d…c394
2 touches
0 conflicts
0x2f5a6614…f293
0x065c9d…c394
2 touches
0 conflicts
0x5527ba11…07a8
0x065c9d…c394
2 touches
0 conflicts
0x5c007b31…1514
0x065c9d…c394
2 touches
0 conflicts
0x9cb85ddb…7406
0x065c9d…c394
2 touches
0 conflicts
0xd058eee1…3265
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