← previous blocknext block →recent activity
Analyzing
Block #75,881,109
10 transactions · 10 stateful · 2026-05-20 18:18:25 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,881,109 · 10 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
2w04w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x892daf6e…48d8
0x065c9d…c394
6 touches
3 conflicts
0x04b3f2c9…827c
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0e19d286…fb83
0x065c9d…c394
3 touches
1 conflict
0xf840e020…295d
0x065c9d…c394
3 touches
1 conflict
0x58c49ce9…5f8f
0x065c9d…c394
2 touches
0 conflicts
0x8777ff60…fc77
0x065c9d…c394
2 touches
0 conflicts
0x8ceb49cb…9ed3
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
3 conflicts on slot 0x892daf6e5d…6d48d8
Audit this contract →
← previous block·next block →recent activity