← previous blocknext block →recent activity
Analyzing
Block #75,297,416
11 transactions · 10 stateful · 2026-05-18 01:14:47 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,297,416 · 11 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
1w04w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2d784efb…682f
0x065c9d…c394
2 touches
0 conflicts
0x416bba49…b399
0x065c9d…c394
2 touches
0 conflicts
0x8ec0ddf1…224d
0x065c9d…c394
2 touches
0 conflicts
0xb741f40e…ec1f
0x065c9d…c394
2 touches
0 conflicts
0xcccc100d…32c3
0x065c9d…c394
2 touches
0 conflicts
0xb1632c2f…d991
0x0a3323…0a3c
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 0xfcb7b8b239…6bebb3
Audit this contract →
← previous block·next block →recent activity