← previous blocknext block →recent activity

Analyzing

Block #106,379,706

29 transactions · 27 stateful · 2026-09-20 05:28:03 UTC

Parallelism

62/100

Blocked

70%

Avg conflicts / tx

2.1

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #106,379,706  ·  29 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x95063b48…269f

0x34b655…2a6f

14 touches
21 conflicts

0x2130a548…c1de

0x34b655…2a6f

12 touches
15 conflicts

0xba33378a…f1df

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x30b822be…f966

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xfad189f8…96e5

0x1b6862…e19c

8 touches
6 conflicts

0x482471ad…122f

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 0x95063b4883…9e269f

← previous block·next block →recent activity