← previous blocknext block →recent activity
Analyzing
Block #75,863,723
11 transactions · 9 stateful · 2026-05-20 16:22:41 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,863,723 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x03d39b4d…7b1f
0x065c9d…c394
2 touches
0 conflicts
0x21c53844…21d9
0x065c9d…c394
2 touches
0 conflicts
0x21e0009b…686f
0x065c9d…c394
2 touches
0 conflicts
0x2d74dfc4…f65e
0x065c9d…c394
2 touches
0 conflicts
0x3562e347…7a12
0x065c9d…c394
2 touches
0 conflicts
0x369e6ca7…742d
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity