<p>Likely this was congestion in getting the transaction adopted rather than the db state being an issue. As for Ignore block, this is normal consensus layer stuff. Another node on network said I have this block, and the node looked at it's current state and decided it's fork was better than the one that block fit on so it never asked for the block.</p>

CC BY-SA 4.0
2022-02-07T14:48:07.467Z
oh yes, seeing all the discussion developing right now on certain type of transaction having a preferential way with SPOs makes it more clear my problems where transactions go through only every so often. I just told that once submitted, the Tx was taken, even if it was going to take more time.. increasing TTL could help?
user3755529
CC BY-SA 4.0
2022-04-21T08:58:14.450Z
SPOs cannot influence the order of the transactions. Most probably what happened is that your TTL wasn't long enough and the deadline slot no had already been surpassed once your transaction was being processed. "Transaction successfully submitted" just means that the transaction passed the initial checks (balanced values, appropriate signatures, sufficient fee, etc) and has been added to the mempool. However, once the transaction actually starts being processed there are other on-chain checks that are performed, such as valid-before, valid-after and any plutus validators.
grim_i_am
CC BY-SA 4.0
2022-02-07T14:08:45.960Z
2022-02-07T14:08:45.960Z
Samuel Leathers
<p>I am trying to delegate a wallet through <code>cardano-cli</code> for most it was going okay, but more recently even though I get the message <code>Transaction successfully submitted.</code> after submitting the transaction, no money gets transferred. The same happens when I try to delegate the wallet.</p>
<p>I noticed that on the <code>cardano-node</code> logs I get something that makes me think some sort of ofrk is happening? <code> Ignoring block already in DB</code></p>
<pre><code>[x-XP:cardano.node.ChainDB:Info:47551] [2022-02-07 13:30:47.64 UTC] before next, messages elided = 94461957158106
[x-XP:cardano.node.ChainDB:Info:47551] [2022-02-07 13:30:47.64 UTC] Ignoring block already in DB: ce7b38a4b05435f4ebe07e1ba52154b6db7131bd062c7809bc5d4ef29b27f3f3 at slot 52674352
[x-XP:cardano.node.Mempool:Info:47597] [2022-02-07 13:30:49.49 UTC] fromList [(&quot;tx&quot;,Object (fromList [(&quot;txid&quot;,String &quot;36f15e82&quot;)])),(&quot;kind&quot;,String &quot;TraceMempoolAddedTx&quot;),(&quot;mempoolSize&quot;,Object (fromList [(&quot;bytes&quot;,Number 399.0),(&quot;numTxs&quot;,Number 1.0)]))]

[x-XP:cardano.node.ChainDB:Info:35] [2022-02-07 13:37:17.56 UTC] Block fits onto some fork: ebf7869a4b082c3d4b2ec60d14f2e8d8f803b9e5a3ab9cd7536927dc9a2b8227 at slot 52674744
[x-XP:cardano.node.ChainDB:Notice:35] [2022-02-07 13:37:17.66 UTC] Switched to a fork, new tip: ebf7869a4b082c3d4b2ec60d14f2e8d8f803b9e5a3ab9cd7536927dc9a2b8227 at slot 52674744


</code></pre>
<p>I tried to delete the entire <code>db</code> and resync the entire <code>cardano-node</code> but as soon as I tried to make a transaction the same as above happenend.</p>
<p>How can I fix this so to have successful transactions again? what coudl I be doing wrong?</p>

CC BY-SA 4.0
2022-02-07T13:42:45.063Z
actually it seem the transactions went through now, so I guess it was indeed a bad database, not sure why it still says `Ignore block` though. Possible that the problem I had earlier was because I was sending transactions in parallel rather than sequentially and made me fork?
user3755529
<cardano-cli><transaction>
Transaction with Cardano-CLI Sumbmits But Nothing Happens
# Transaction with Cardano-CLI Sumbmits But Nothing Happens

(Asked by: username_0 on 2022-02-07)

I am trying to delegate a wallet through cardano-cli for most it was going okay, but more recently even though I get the message Transaction successfully submitted. after submitting the transaction, no money gets transferred. The same happens when I try to delegate the wallet.
I noticed that on the cardano-node logs I get something that makes me think some sort of ofrk is happening?  Ignoring block already in DB
[x-XP:cardano.node.ChainDB:Info:47551] [2022-02-07 13:30:47.64 UTC] before next, messages elided = 94461957158106
[x-XP:cardano.node.ChainDB:Info:47551] [2022-02-07 13:30:47.64 UTC] Ignoring block already in DB: ce7b38a4b05435f4ebe07e1ba52154b6db7131bd062c7809bc5d4ef29b27f3f3 at slot 52674352
[x-XP:cardano.node.Mempool:Info:47597] [2022-02-07 13:30:49.49 UTC] fromList [("tx",Object (fromList [("txid",String "36f15e82")])),("kind",String "TraceMempoolAddedTx"),("mempoolSize",Object (fromList [("bytes",Number 399.0),("numTxs",Number 1.0)]))]

[x-XP:cardano.node.ChainDB:Info:35] [2022-02-07 13:37:17.56 UTC] Block fits onto some fork: ebf7869a4b082c3d4b2ec60d14f2e8d8f803b9e5a3ab9cd7536927dc9a2b8227 at slot 52674744
[x-XP:cardano.node.ChainDB:Notice:35] [2022-02-07 13:37:17.66 UTC] Switched to a fork, new tip: ebf7869a4b082c3d4b2ec60d14f2e8d8f803b9e5a3ab9cd7536927dc9a2b8227 at slot 52674744



I tried to delete the entire db and resync the entire cardano-node but as soon as I tried to make a transaction the same as above happenend.
How can I fix this so to have successful transactions again? what coudl I be doing wrong?

**Tags:** cardano-cli, transaction
> **Comments:**
> **username_0**: actually it seem the transactions went through now, so I guess it was indeed a bad database, not sure why it still says `Ignore block` though. Possible that the problem I had earlier was because I was sending transactions in parallel rather than sequentially and made me fork?  

---

## 1 answers

### Answer by username_1 on 2022-02-07. Score: 0 | Accepted answer

Likely this was congestion in getting the transaction adopted rather than the db state being an issue. As for Ignore block, this is normal consensus layer stuff. Another node on network said I have this block, and the node looked at it's current state and decided it's fork was better than the one that block fit on so it never asked for the block.

> **Comments:**
> **username_0**: oh yes, seeing all the discussion developing right now on certain type of transaction having a preferential way with SPOs makes it more clear my problems where transactions go through only every so often. I just told that once submitted, the Tx was taken, even if it was going to take more time.. increasing TTL could help?  
> **username_2**: SPOs cannot influence the order of the transactions. Most probably what happened is that your TTL wasn't long enough and the deadline slot no had already been surpassed once your transaction was being processed. "Transaction successfully submitted" just means that the transaction passed the initial checks (balanced values, appropriate signatures, sufficient fee, etc) and has been added to the mempool. However, once the transaction actually starts being processed there are other on-chain checks that are performed, such as valid-before, valid-after and any plutus validators.  

---

