← previous blocknext block →recent activity
Analyzing
Block #76,570,212
14 transactions · 11 stateful · 2026-05-23 22:47:32 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,570,212 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc4f1f14…aa5f
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0x0aa885fa…a3d1
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0000
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…0001
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…000c
0x2b37ef…0bdc
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
3 conflicts on slot 0xcc4f1f1446…7caa5f
Audit this contract →
← previous block·next block →recent activity