← previous blocknext block →recent activity

Analyzing

Block #106,389,220

21 transactions · 21 stateful · 2026-09-20 06:15:56 UTC

Parallelism

81/100

Blocked

24%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,389,220  ·  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

0x41869112…4809

0x34b655…2a6f

8 touches
6 conflicts

0x02397184…a64f

0x34b655…2a6f

4 touches
1 conflict

0x1b25f260…c429

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x628e0d85…2e5c

0x99c7a7…8bf0

4 touches
1 conflict

0x8401a9f1…e868

0x754704…b603

4 touches
1 conflict

0x363d5ac3…a29d

0x99c7a7…8bf0

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 0x41869112c5…674809

← previous block·next block →recent activity