← previous blocknext block →recent activity

Analyzing

Block #75,268,785

29 transactions · 18 stateful · 2026-05-17 22:03:06 UTC

Parallelism

90/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,268,785  ·  29 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

0xfe2bac2b…2cec

0x065c9d…c394

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x79a41cb1…2da0

0xd32edf…ff58

5 touches
3 conflicts

0x0520da1d…c88e

0x34b655…2a6f

4 touches
1 conflict

0x0c89c370…e9ef

0x34b655…2a6f

4 touches
1 conflict

0x801a6e57…d85c

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0x8aa1941d…2988

0x34b655…2a6f

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 0xfe2bac2b2f…482cec

← previous block·next block →recent activity