← previous blocknext block →recent activity
Analyzing
Block #75,199,436
8 transactions · 7 stateful · 2026-05-17 14:19:36 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,199,436 · 8 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
3w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7aa2ccc3…6cc1
0x065c9d…c394
4 touches
1 conflict
0xca8aa673…edaf
0x065c9d…c394
4 touches
1 conflict
0x3b442234…a938
0x065c9d…c394
3 touches
1 conflict
0x6d355c86…fec6
0x065c9d…c394
3 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0x8ec90101…a8a2
0x065c9d…c394
2 touches
0 conflicts
0x9d4d6f21…283c
0x065c9d…c394
2 touches
0 conflicts
0xba38536d…2b7d
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 0x7aa2ccc353…ff6cc1
Audit this contract →
← previous block·next block →recent activity