← previous blocknext block →recent activity

Analyzing

Block #106,403,825

22 transactions · 22 stateful · 2026-09-20 07:29:25 UTC

Parallelism

64/100

Blocked

41%

Avg conflicts / tx

1.64

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #106,403,825  ·  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

0x799f4636…f628

0x34b655…2a6f

16 touches
28 conflicts

0xfdd131fa…dbdb

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x54f7f60f…43cc

0x34b655…2a6f

8 touches
6 conflicts

0x1b25f260…c429

0x34b655…2a6f

8 touches
6 conflicts

0xac0b4a08…faae

0x34b655…2a6f

8 touches
6 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

6 touches
3 conflicts

0xdac9c1bc…c189

0x34b655…2a6f

6 touches
3 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 0x799f4636c0…6af628

← previous block·next block →recent activity