← previous blocknext block →recent activity

Analyzing

Block #106,550,554

19 transactions · 16 stateful · 2026-09-20 19:47:56 UTC

Parallelism

74/100

Blocked

56%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,550,554  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x1b25f260…c429

0x34b655…2a6f

8 touches
6 conflicts

0xec2a8d79…70cb

0x34b655…2a6f

8 touches
6 conflicts

0xa579bcf9…8820

0x34b655…2a6f

8 touches
6 conflicts

0x6b267bdf…b173

0x34b655…2a6f

8 touches
6 conflicts

0x2c2761c0…476e

0x34b655…2a6f

6 touches
3 conflicts

0x0fcabe0b…a614

0x34b655…2a6f

6 touches
3 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

6 touches
3 conflicts

0xba65d335…5a78

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

6 conflicts on slot 0x1b25f26097…52c429

← previous block·next block →recent activity