← previous blocknext block →recent activity

Analyzing

Block #84,081,815

23 transactions · 20 stateful · 2026-06-27 17:59:06 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

1.09

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #84,081,815  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x0b16149e…7d4d

0x065c9d…c394

10 touches
10 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x52f0d02d…6433

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 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

10 conflicts on slot 0x0b16149e0d…887d4d

← previous block·next block →recent activity