← previous blocknext block →recent activity

Analyzing

Block #106,947,013

21 transactions · 19 stateful · 2026-09-22 05:04:22 UTC

Parallelism

81/100

Blocked

32%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,947,013  ·  21 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

0x4bb6a0b8…25aa

0x34b655…2a6f

8 touches
6 conflicts

0x8590b692…b267

0x34b655…2a6f

6 touches
3 conflicts

0xfcc8f826…7c5f

0x34b655…2a6f

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x49b9fdd5…9c16

0x34b655…2a6f

4 touches
1 conflict

0x4e58deff…c5d0

0x34b655…2a6f

4 touches
1 conflict

0x65b3fc65…e24e

0x34b655…2a6f

4 touches
1 conflict

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 0x4bb6a0b868…8825aa

← previous block·next block →recent activity