← previous blocknext block →recent activity

Analyzing

Block #106,810,566

17 transactions · 17 stateful · 2026-09-21 17:37:34 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,810,566  ·  17 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

0xd59791ce…f29e

0x34b655…2a6f

6 touches
3 conflicts

0xcd47df3f…a2e0

0x34b655…2a6f

6 touches
3 conflicts

0x25957369…c648

0x34b655…2a6f

6 touches
3 conflicts

0x88e771e8…7d4a

0x34b655…2a6f

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0x2c2db8e9…fdc7

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xccec1087…2868

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

3 conflicts on slot 0xd59791ceb4…2cf29e

← previous block·next block →recent activity