← previous blocknext block →recent activity

Analyzing

Block #106,110,230

21 transactions · 19 stateful · 2026-09-19 06:51:48 UTC

Parallelism

76/100

Blocked

37%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,110,230  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xdfc7e6c9…04c2

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x06ce5d4b…c122

0x34ae4d…3fc5

2 touches
0 conflicts

0x64a785e4…0110

0x34b655…2a6f

2 touches
0 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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity