← previous blocknext block →recent activity
Analyzing
Block #75,129,884
9 transactions · 6 stateful · 2026-05-17 06:35:12 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,129,884 · 9 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20ef23d9…a557
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc472cf62…c5c3
0x065c9d…c394
3 touches
1 conflict
0x4016678d…7f94
0x065c9d…c394
2 touches
0 conflicts
0x5a456a3e…08e0
0x065c9d…c394
2 touches
0 conflicts
0x76afe200…a6d8
0x065c9d…c394
2 touches
0 conflicts
0x8cca21a1…e550
0x065c9d…c394
2 touches
0 conflicts
0x9c575c2c…eea6
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 0x20ef23d93e…35a557
Audit this contract →
← previous block·next block →recent activity