← previous blocknext block →recent activity

Analyzing

Block #106,452,614

30 transactions · 28 stateful · 2026-09-20 11:35:02 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.53

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,452,614  ·  30 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

0x282d0473…a801

0x34b655…2a6f

10 touches
10 conflicts

0x8d664414…3344

0x34b655…2a6f

8 touches
6 conflicts

0x810a3aa2…0227

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x2c2db8e9…fdc7

0x34b655…2a6f

4 touches
1 conflict

0x33626d48…31b8

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x7dd96c96…7335

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

10 conflicts on slot 0x282d04739e…97a801

← previous block·next block →recent activity