← previous blocknext block →recent activity

Analyzing

Block #106,772,653

32 transactions · 25 stateful · 2026-09-21 14:26:42 UTC

Parallelism

81/100

Blocked

56%

Avg conflicts / tx

1.13

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,772,653  ·  32 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

0xaad6be10…0801

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0xcc4f1f14…aa5f

0x065c9d…c394

10 touches
10 conflicts

0xdfa159d0…1576

0x065c9d…c394

10 touches
10 conflicts

0x2c0dec2a…687a

0xd32edf…ff58

7 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xb87af72a…aef6

0x2a68ba…90c5

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: MarginAccount

15 conflicts on slot 0xaad6be10ae…2c0801

← previous block·next block →recent activity