← previous blocknext block →recent activity
Analyzing
Block #75,199,948
9 transactions · 8 stateful · 2026-05-17 14:23:01 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,199,948 · 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41a8f136…fb51
0x065c9d…c394
4 touches
1 conflict
0xd21c95e2…74c6
0x065c9d…c394
3 touches
1 conflict
0x1fc5a6a2…5c32
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x605d66ef…b701
0x065c9d…c394
2 touches
0 conflicts
0x7aa2ccc3…6cc1
0x065c9d…c394
2 touches
0 conflicts
0x87b8b467…af5b
0x065c9d…c394
2 touches
0 conflicts
0xa3a49bd9…3b11
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 0x41a8f13612…fdfb51
Audit this contract →
← previous block·next block →recent activity