← previous blocknext block →recent activity
Analyzing
Block #75,685,873
14 transactions · 8 stateful · 2026-05-19 20:37:01 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,685,873 · 14 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
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0x4c43e9fb…5d5d
0x065c9d…c394
3 touches
1 conflict
0x151f8a43…8d7e
0xd32edf…ff58
3 touches
1 conflict
0xa4a47e79…a9b1
0x065c9d…c394
2 touches
0 conflicts
0xe9b38a3c…c4d3
0x065c9d…c394
2 touches
0 conflicts
0xebec1672…823d
0x065c9d…c394
2 touches
0 conflicts
0xf95057c7…eba1
0x065c9d…c394
2 touches
0 conflicts
0xff6f7279…471e
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 0xcc4f1f1446…7caa5f
Audit this contract →
← previous block·next block →recent activity