← previous blocknext block →recent activity

Analyzing

Block #106,429,280

21 transactions · 19 stateful · 2026-09-20 09:37:31 UTC

Parallelism

76/100

Blocked

53%

Avg conflicts / tx

1.33

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,429,280  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x98574f96…dea5

0x34b655…2a6f

8 touches
6 conflicts

0x0ed7cc0b…ee52

0x34b655…2a6f

8 touches
6 conflicts

0x17953a45…96a1

0x34b655…2a6f

8 touches
6 conflicts

0x1b25f260…c429

0x34b655…2a6f

8 touches
6 conflicts

0x2c2761c0…476e

0x34b655…2a6f

8 touches
6 conflicts

0xb6c3be06…1644

0x34b655…2a6f

8 touches
6 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

8 touches
6 conflicts

0x6771eae2…7014

0x34b655…2a6f

8 touches
6 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: Perpl

6 conflicts on slot 0x98574f96f8…e4dea5

← previous block·next block →recent activity