← previous blocknext block →recent activity

Analyzing

Block #77,182,501

22 transactions · 18 stateful · 2026-05-26 18:43:50 UTC

Parallelism

82/100

Blocked

44%

Avg conflicts / tx

0.73

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #77,182,501  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x95523e2a…4c01

0x065c9d…c394

6 touches
3 conflicts

0xba5743c7…21c1

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x56216150…4efd

0xd32edf…ff58

5 touches
3 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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity