← previous blocknext block →recent activity
Analyzing
Block #75,017,025
10 transactions · 6 stateful · 2026-05-16 18:02:28 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,017,025 · 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
1w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xfb2a00fd…8618
0x065c9d…c394
3 touches
1 conflict
0xc2ef7224…f3fa
0x065c9d…c394
3 touches
1 conflict
0x4332552b…26be
0x065c9d…c394
3 touches
1 conflict
0xb415f925…3f0f
0x065c9d…c394
3 touches
1 conflict
0x551057cd…3c97
0x065c9d…c394
2 touches
0 conflicts
0xad5f6e76…16ff
0x065c9d…c394
2 touches
0 conflicts
0xb254f737…ead1
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity