← previous blocknext block →recent activity

Analyzing

Block #83,580,992

42 transactions · 34 stateful · 2026-06-25 10:19:00 UTC

Parallelism

79/100

Blocked

53%

Avg conflicts / tx

1.67

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #83,580,992  ·  42 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x2886e2bc…6ab8

0x065c9d…c394

16 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x1fa50c3e…4c7e

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002a

0x1b6862…e19c

8 touches
6 conflicts

0xc3483764…f298

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

28 conflicts on slot 0x2886e2bc57…316ab8

← previous block·next block →recent activity