← previous blocknext block →recent activity

Analyzing

Block #102,411,554

25 transactions · 22 stateful · 2026-09-06 07:37:31 UTC

Parallelism

84/100

Blocked

27%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,411,554  ·  25 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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x84f1799f…9466

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xdfa159d0…1576

0x065c9d…c394

4 touches
1 conflict

0x08e8f2c9…a11a

0x34b655…2a6f

4 touches
1 conflict

0x1a2055c7…9054

0x34b655…2a6f

4 touches
1 conflict

0x4ec9ff52…e6f7

0x34b655…2a6f

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 0x0000000000…00003d

← previous block·next block →recent activity