← previous blocknext block →recent activity

Analyzing

Block #106,200,519

26 transactions · 25 stateful · 2026-09-19 14:26:12 UTC

Parallelism

62/100

Blocked

56%

Avg conflicts / tx

1.92

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #106,200,519  ·  26 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x61cd438d…536f

0x34b655…2a6f

14 touches
21 conflicts

0x1b25f260…c429

0x34b655…2a6f

10 touches
10 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

10 touches
10 conflicts

0xf195ad96…e0c3

0x34b655…2a6f

10 touches
10 conflicts

0xe5eb3c33…0e3a

0x34b655…2a6f

10 touches
10 conflicts

0xfe39a1f7…8eb0

0x34b655…2a6f

8 touches
6 conflicts

0x1d351a9b…f2dd

0x34b655…2a6f

8 touches
6 conflicts

0x23a320fb…cbd7

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

21 conflicts on slot 0x61cd438db3…11536f

← previous block·next block →recent activity