TX's Maturity Event

Here is the First TX's Maturity Event

{  type: 'maturity',  data: {    id: Hash { __wbg_ptr: 4428848 },    unixtimeMsec: 1715232640551n,    value: 483234394625n,    blockDaaScore: 105987516n,    network: { type: 1, suffix: 11, id: 'testnet-11' },    note: undefined,    metadata: undefined,    binding: {      type: 'custom',      id: 'af5570f5a1810b7af78caf4bc70a660f0df51e42baf91d4de5b2328de0e83dfc'    },    data: { utxoEntries: [Array], value: 483234394625 },    type: 'external'  } }

This is the Second Maturity event of the same TX

{  type: 'maturity',  data: {    id: Hash { __wbg_ptr: 4378600 },    unixtimeMsec: 1715232650268n,    value: 476791519847n,    blockDaaScore: 106569345n,    network: { type: 1, suffix: 11, id: 'testnet-11' },    note: undefined,    metadata: undefined,    binding: {      type: 'custom',      id: 'af5570f5a1810b7af78caf4bc70a660f0df51e42baf91d4de5b2328de0e83dfc'    },    data: { utxoEntries: [Array], value: 476791519847 },    type: 'incoming'  } }

[13:3

The first one (type:external) comes right away when submittion is executed.

The second one (incoming) comes when it is really ready to process the next tx