← previous blocknext block →recent activity

Analyzing

Block #106,952,011

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

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,952,011  ·  21 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

0x0f9b300c…8824

0x34b655…2a6f

8 touches
6 conflicts

0xfcc8f826…7c5f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0x67c323c8…1ab3

0x34b655…2a6f

6 touches
3 conflicts

0xa2a4e273…66a2

0x40c49f…2af0

4 touches
1 conflict

0x3eb48ea2…eef2

0x34b655…2a6f

4 touches
1 conflict

0x51087f5a…61f7

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 0x0f9b300c83…318824

← previous block·next block →recent activity