← previous blocknext block →recent activity
Analyzing
Block #76,231,345
8 transactions · 6 stateful · 2026-05-22 09:11:18 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,231,345 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4bc9c83a…663c
0x065c9d…c394
2 touches
0 conflicts
0x557800fc…efb8
0x065c9d…c394
2 touches
0 conflicts
0xa5f7b6be…261c
0x065c9d…c394
2 touches
0 conflicts
0xc9657ab1…8737
0x065c9d…c394
2 touches
0 conflicts
0xd6c4c102…faa8
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