← previous blocknext block →recent activity
Analyzing
Block #75,955,058
7 transactions · 5 stateful · 2026-05-21 02:30:31 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,955,058 · 7 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x98db6962…9e41
0x065c9d…c394
3 touches
1 conflict
0xa553d0a7…311c
0x065c9d…c394
3 touches
1 conflict
0x18b9bf34…31af
0x065c9d…c394
2 touches
0 conflicts
0x2d776eed…2f89
0x065c9d…c394
2 touches
0 conflicts
0x2ef7f1ae…b46c
0x065c9d…c394
2 touches
0 conflicts
0x76312195…8c2b
0x065c9d…c394
2 touches
0 conflicts
0x94c6f2e2…cf06
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