← previous blocknext block →recent activity

Analyzing

Block #102,477,418

20 transactions · 19 stateful · 2026-09-06 13:11:09 UTC

Parallelism

80/100

Blocked

37%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,477,418  ·  20 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

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x1a2055c7…9054

0x34b655…2a6f

6 touches
3 conflicts

0x1d351a9b…f2dd

0x34b655…2a6f

6 touches
3 conflicts

0x70d81211…f49f

0x34b655…2a6f

6 touches
3 conflicts

0x9b22efd2…c692

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity