← previous blocknext block →recent activity

Analyzing

Block #106,027,648

19 transactions · 16 stateful · 2026-09-18 23:56:12 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,027,648  ·  19 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

0x045532dd…4b7d

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0xb75367ff…a2b7

0x34b655…2a6f

6 touches
3 conflicts

0x0247122b…a1ac

0x6f6493…b480

5 touches
3 conflicts

0x092a3ee5…9d23

0x6f6493…b480

5 touches
3 conflicts

0x1bd4c7cb…f222

0x6f6493…b480

5 touches
3 conflicts

0x1c48e206…8dc9

0x6f6493…b480

5 touches
3 conflicts

0x29d89852…5afe

0x6f6493…b480

5 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 0x045532dd4b…244b7d

← previous block·next block →recent activity