<p>Transactions are being included into blocks in 1 minute in average. Longer you wait - higher a chance that a double-spending won't happen. There is no such a number that guarantees 100% irreversibility.</p>

<p>1 confirmation is not secure at all. 10 confirmations is recommended for small amounts, 720 confirmations - for big ones.</p>

CC BY-SA 3.0
2014-07-08T18:08:37.747Z
i just sent 8 nxt to one of my wallets and its been 5-10 minutes and i still didn't get any confirmations yet. but it does show up that its sent in the other wallet.
Patoshi パトシ
CC BY-SA 3.0
2014-07-08T18:18:06.093Z
1 minute is AVERAGE time, real time varies from seconds to an hour. Also it can be a local node issue related to incorrect time/timezone, bad connection or a client software bug.
Come-from-Beyond
CC BY-SA 3.0
2014-07-08T18:05:36.513Z
2014-07-08T18:05:36.513Z
Come-from-Beyond
<p>what is the block time to get my transaction confirmation? Do i still have to wait 10+ minutes to make sure a double spend didnt happen?</p>

<block><nxt>
What is the block / confirmation time for NXT coin?
Patoshi パトシ
# What is the block / confirmation time for NXT coin?

(Asked by: username_0 on 2014-07-08)

what is the block time to get my transaction confirmation? Do i still have to wait 10+ minutes to make sure a double spend didnt happen?

**Tags:** block, nxt


---

## 1 answers

### Answer by username_1 on 2014-07-08. Score: 2 | Accepted answer

Transactions are being included into blocks in 1 minute in average. Longer you wait - higher a chance that a double-spending won't happen. There is no such a number that guarantees 100% irreversibility.

1 confirmation is not secure at all. 10 confirmations is recommended for small amounts, 720 confirmations - for big ones.

> **Comments:**
> **username_0**: i just sent 8 nxt to one of my wallets and its been 5-10 minutes and i still didn't get any confirmations yet. but it does show up that its sent in the other wallet.  
> **username_1**: 1 minute is AVERAGE time, real time varies from seconds to an hour. Also it can be a local node issue related to incorrect time/timezone, bad connection or a client software bug.  

---

