← previous blocknext block →recent activity

Analyzing

Block #77,784,403

39 transactions · 27 stateful · 2026-05-29 13:38:41 UTC

Parallelism

69/100

Blocked

63%

Avg conflicts / tx

1.18

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #77,784,403  ·  39 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xce827910…ff22

0x065c9d…c394

10 touches
10 conflicts

0x351ee25b…1edb

0xd32edf…ff58

9 touches
10 conflicts

0x49cbdb1b…bda4

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001e

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002e

0x1b6862…e19c

8 touches
6 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

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity