← previous blocknext block →recent activity

Analyzing

Block #106,164,723

20 transactions · 20 stateful · 2026-09-19 11:26:03 UTC

Parallelism

70/100

Blocked

45%

Avg conflicts / tx

1.3

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,164,723  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x81b402ec…b23b

0x34b655…2a6f

10 touches
10 conflicts

0xb550abea…2729

0x34b655…2a6f

8 touches
6 conflicts

0x1b25f260…c429

0x34b655…2a6f

8 touches
6 conflicts

0xe098738f…9bbe

0x34b655…2a6f

8 touches
6 conflicts

0x42260953…76b3

0x34b655…2a6f

8 touches
6 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

8 touches
6 conflicts

0xba1edffb…323e

0x34b655…2a6f

8 touches
6 conflicts

0xdf64e5e6…75e8

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

10 conflicts on slot 0x81b402ec5c…a2b23b

← previous block·next block →recent activity