← previous blocknext block →recent activity
Analyzing
Block #75,988,206
8 transactions · 6 stateful · 2026-05-21 06:11:22 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,988,206 · 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ed9c145…2d7d
0x065c9d…c394
4 touches
1 conflict
0x42186c9f…b17c
0x065c9d…c394
3 touches
1 conflict
0x96fac984…2766
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2bd93c3a…44fc
0x065c9d…c394
2 touches
0 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
2 touches
0 conflicts
0x9bf064a6…4f04
0x2a68ba…90c5
2 touches
0 conflicts
0x3f7a1f04…70bb
0x34b655…2a6f
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 0x4ed9c14553…fd2d7d
Audit this contract →
← previous block·next block →recent activity