← previous blocknext block →recent activity

Analyzing

Block #106,408,236

22 transactions · 21 stateful · 2026-09-20 07:51:37 UTC

Parallelism

64/100

Blocked

38%

Avg conflicts / tx

0.95

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #106,408,236  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x09df280e…44f2

0x34b655…2a6f

4 touches
1 conflict

0x1b25f260…c429

0x34b655…2a6f

4 touches
1 conflict

0x49b9fdd5…9c16

0x34b655…2a6f

4 touches
1 conflict

0x524f0872…0d12

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity