← previous blocknext block →recent activity

Analyzing

Block #106,200,009

20 transactions · 16 stateful · 2026-09-19 14:23:37 UTC

Parallelism

80/100

Blocked

44%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,200,009  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00c0d1ad…9d70

0x6f6493…b480

7 touches
6 conflicts

0x04309565…10c4

0x6f6493…b480

7 touches
6 conflicts

0x04d26e3a…4c72

0x6f6493…b480

7 touches
6 conflicts

0x0b6c171c…416d

0x6f6493…b480

7 touches
6 conflicts

0x166f3027…ec62

0x6f6493…b480

7 touches
6 conflicts

0x1829115d…5322

0x6f6493…b480

7 touches
6 conflicts

0x18fd9430…19e3

0x6f6493…b480

7 touches
6 conflicts

0x1a808bc0…c955

0x6f6493…b480

7 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: 0x6f6493e3…08b480

6 conflicts on slot 0x00c0d1ad39…399d70

← previous block·next block →recent activity