← previous blocknext block →recent activity
Analyzing
Block #76,594,294
7 transactions · 5 stateful · 2026-05-24 01:27:47 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,594,294 · 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99b16765…590d
0x065c9d…c394
4 touches
1 conflict
0x5976a596…6417
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9d00d35d…4fe0
0x065c9d…c394
3 touches
1 conflict
0x1d1b8a3e…f370
0x065c9d…c394
2 touches
0 conflicts
0x8041a6a4…b5ed
0x065c9d…c394
2 touches
0 conflicts
0xdfa159d0…1576
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x1d1325…2305
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 0x99b16765be…91590d
Audit this contract →
← previous block·next block →recent activity