← previous blocknext block →recent activity

Analyzing

Block #106,373,441

13 transactions · 12 stateful · 2026-09-20 04:56:31 UTC

Parallelism

69/100

Blocked

42%

Avg conflicts / tx

0.69

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,373,441  ·  13 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

0xc9a6e112…69cc

0x34b655…2a6f

8 touches
6 conflicts

0xd29e547b…a1dd

0x34b655…2a6f

6 touches
3 conflicts

0xac0b4a08…faae

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x09e0690d…6e3d

0xe52b14…7230

4 touches
1 conflict

0x17bbe4f8…08c5

0xe52b14…7230

4 touches
1 conflict

0x3cebc8f1…975c

0xe52b14…7230

4 touches
1 conflict

0x58733c38…f2cd

0xe52b14…7230

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 0xc9a6e112ce…9769cc

← previous block·next block →recent activity