← previous blocknext block →recent activity

Analyzing

Block #105,855,618

23 transactions · 21 stateful · 2026-09-18 09:29:21 UTC

Parallelism

74/100

Blocked

43%

Avg conflicts / tx

0.91

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #105,855,618  ·  23 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

0x802fc4dd…3bca

0x34b655…2a6f

8 touches
6 conflicts

0xfefb0189…f726

0x34b655…2a6f

8 touches
6 conflicts

0xf8e6479f…f193

0x34b655…2a6f

8 touches
6 conflicts

0xeff9ac99…9e3d

0x34b655…2a6f

8 touches
6 conflicts

0xab981df1…2941

0x34b655…2a6f

8 touches
6 conflicts

0x80398c66…f3cc

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0x29fc3fce…1d6e

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 0x802fc4dd44…983bca

← previous block·next block →recent activity