← previous blocknext block →recent activity

Analyzing

Block #77,554,348

18 transactions · 16 stateful · 2026-05-28 12:04:15 UTC

Parallelism

83/100

Blocked

44%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #77,554,348  ·  18 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

0xce827910…ff22

0x065c9d…c394

4 touches
1 conflict

0x78ce7d20…2a3f

0xa6afd3…d132

4 touches
1 conflict

0x13350543…ebf2

0xa6afd3…d132

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xf9b8ae99…32b4

0x34b655…2a6f

4 touches
1 conflict

0x52e69143…95ad

0x065c9d…c394

4 touches
1 conflict

0xf9b8ae99…32b3

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

1 conflict on slot 0xce827910a4…82ff22

← previous block·next block →recent activity