An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.
7c5e0bd7d4f6db0e447a893da54d25c55c8d8775d7d49e8a3c7a6767eef647bc
Both payments are on their chains and locked to the same secret hash d78c6c57b2d09047d4fd0f94a5299dfea969ea6c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 7c5e0bd7d4f6db0e447a893da54d25c55c8d8775d7d49e8a3c7a6767eef647bc
aad00b5e6bac70526fbfe497fc280c00d2948e3e1b9a20e08170cea3355401aa
Both payments are on their chains and locked to the same secret hash d78c6c57b2d09047d4fd0f94a5299dfea969ea6c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · b7be8fc14f3f11e0084091621216761f0bf69fbce878f9fea62448187a776b57
- TakerPaymentReceived · aad00b5e6bac70526fbfe497fc280c00d2948e3e1b9a20e08170cea3355401aa
- TakerPaymentSpent · aa4a12fd551c6893238a28e8cf4cb14531d560b6e1df945d9b0ae45ad750de16
Reported by kdf-statsdb.