← previous blocknext block →recent activity

Analyzing

Block #76,603,069

20 transactions · 12 stateful · 2026-05-24 02:26:12 UTC

Parallelism

85/100

Blocked

50%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #76,603,069  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x3b247d55…1575

0xd32edf…ff58

5 touches
3 conflicts

0x3e1d1c96…29ab

0x065c9d…c394

4 touches
1 conflict

0xcc4f1f14…aa5f

0x065c9d…c394

4 touches
1 conflict

0xdfa159d0…1576

0x065c9d…c394

4 touches
1 conflict

0xa17ec269…7cdd

0x1d1325…2305

4 touches
1 conflict

0x1a3ab0a2…d904

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

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 0x0000000000…00003d

← previous block·next block →recent activity