← previous blocknext block →recent activity

Analyzing

Block #105,869,859

24 transactions · 21 stateful · 2026-09-18 10:41:00 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #105,869,859  ·  24 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0x3a02129f…9eaf

0x34b655…2a6f

6 touches
3 conflicts

0x14e0dbd0…c4cf

0x6f6493…b480

6 touches
3 conflicts

0x31e172e0…3920

0x6f6493…b480

6 touches
3 conflicts

0x7bbf326e…754b

0x6f6493…b480

6 touches
3 conflicts

0x86ec9f85…5c30

0x6f6493…b480

6 touches
3 conflicts

0x9c31d6dc…8ccf

0x6f6493…b480

6 touches
3 conflicts

0x448fdf2a…fab4

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

3 conflicts on slot 0x8bf661cb38…d4bcd2

← previous block·next block →recent activity