<p>The default TTL for transactions submitted via cardano-wallet is 7200 slots, or 2 hours. You can increase this by adding a <code>--ttl &lt;INTEGER&gt;</code> flag when you create the transaction on cardano-wallet. The best way to check if the transaction was included on-chain is to then check back on chain after the selected time has elapsed to see if it was included in a block. It shouldn't be too hard to automate this process either.</p>
<p>I expanded a bit in <a href="https://cardano.stackexchange.com/questions/6774/received-the-transaction-id-but-the-transaction-never-happened/6776#6776">this</a> post.</p>

CC BY-SA 4.0
2022-01-24T01:28:31.040Z
2022-01-24T01:28:31.040Z
zhekson
<p>Recently Cardano has come under heavy load. The consequences have been that some of our transactions which appear to have submitted successfully to the blockchain do not actually end up on the blockchain. By 'appear to' I mean we submit a transaction using the <code>cardano-wallet</code> api which returns a successful response.</p>
<p>For example:</p>
<pre><code>  r = requests.post(f'http://{app.config[&quot;WALLET_API_URL&quot;]}/v2/wallets/{app.config[&quot;WALLET_ID&quot;]}/transactions', json=outbound_tx.body)
</code></pre>
<p>Now, sometimes when we manually follow up on these tx ids it turns out they never show up in cardano explorer. More directly, they never appear on chain. This never happened before the recent congestion so we assume some transactions are being dropped by the chain.</p>
<p>What is the best practice for following up on submitted transactions to ensure they have, in fact, posted to the chain?</p>

<wallet><transaction>
How to handle tx dropped due to congested network?
# How to handle tx dropped due to congested network?

(Asked by: username_0 on 2022-01-23)

Recently Cardano has come under heavy load. The consequences have been that some of our transactions which appear to have submitted successfully to the blockchain do not actually end up on the blockchain. By 'appear to' I mean we submit a transaction using the cardano-wallet api which returns a successful response.
For example:
  r = requests.post(f'http://{app.config["WALLET_API_URL"]}/v2/wallets/{app.config["WALLET_ID"]}/transactions', json=outbound_tx.body)

Now, sometimes when we manually follow up on these tx ids it turns out they never show up in cardano explorer. More directly, they never appear on chain. This never happened before the recent congestion so we assume some transactions are being dropped by the chain.
What is the best practice for following up on submitted transactions to ensure they have, in fact, posted to the chain?

**Tags:** wallet, transaction

---

## 1 answers

### Answer by username_1 on 2022-01-24. Score: 1

The default TTL for transactions submitted via cardano-wallet is 7200 slots, or 2 hours. You can increase this by adding a `--ttl`  flag when you create the transaction on cardano-wallet. The best way to check if the transaction was included on-chain is to then check back on chain after the selected time has elapsed to see if it was included in a block. It shouldn't be too hard to automate this process either.

I expanded a bit in [this](https://cardano.stackexchange.com/questions/6774/received-the-transaction-id-but-the-transaction-never-happened/6776#6776) post.


---

