← previous blocknext block →recent activity

Analyzing

Block #106,403,565

21 transactions · 21 stateful · 2026-09-20 07:28:07 UTC

Parallelism

57/100

Blocked

67%

Avg conflicts / tx

2.05

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #106,403,565  ·  21 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x97d5c954…ea05

0x34b655…2a6f

16 touches
28 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0xfdd131fa…dbdb

0x34b655…2a6f

12 touches
15 conflicts

0x6c32b694…d019

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…002a

0x1b6862…e19c

8 touches
6 conflicts

0x2b093939…9085

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x4984f7be…d515

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

28 conflicts on slot 0x97d5c954bf…f2ea05

← previous block·next block →recent activity