← previous blocknext block →recent activity
Analyzing
Block #75,523,576
8 transactions · 7 stateful · 2026-05-19 02:34:02 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,523,576 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39b16da9…585d
0x065c9d…c394
4 touches
1 conflict
0xf560c53b…b7b1
0x065c9d…c394
3 touches
1 conflict
0xa3830f76…1180
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1d17d5a5…9e95
0x065c9d…c394
2 touches
0 conflicts
0x5f77d607…2c84
0x065c9d…c394
2 touches
0 conflicts
0x892daf6e…48d8
0x065c9d…c394
2 touches
0 conflicts
0xdf268f1d…9d2e
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 0x39b16da984…d4585d
Audit this contract →
← previous block·next block →recent activity