← previous blocknext block →recent activity

Analyzing

Block #84,193,829

18 transactions · 17 stateful · 2026-06-28 06:24:54 UTC

Parallelism

67/100

Blocked

53%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #84,193,829  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x56785e37…a197

0x065c9d…c394

8 touches
6 conflicts

0xe75cebb6…6b36

0x065c9d…c394

8 touches
6 conflicts

0xab86573c…682e

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001e

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002e

0x1b6862…e19c

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

6 conflicts on slot 0x56785e3778…33a197

← previous block·next block →recent activity