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.
0a804ad41239bb2e3ae9b2face7ec402fb4d06df8ba00bd6fef508765b18e989
Both payments are on their chains and locked to the same secret hash 417bf26179f9a040b7a3ff326daee0f649849523, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 0a804ad41239bb2e3ae9b2face7ec402fb4d06df8ba00bd6fef508765b18e989
- MakerPaymentSpent: 9573693fd969035f3b37e6b81a9c90f8cd4df85f78af84664526e264d41feb4d
4a0fed5bd99c4b7ac45b286d8322a6fb444a32baa380e6bcb9bb67a8a372e0f7
Both payments are on their chains and locked to the same secret hash 417bf26179f9a040b7a3ff326daee0f649849523, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 91b61bfa6fd646554938acba0e866ee67b0c8a3ff54a3db2e037d888b71a035e
- TakerPaymentSent · TakerPaymentReceived: 4a0fed5bd99c4b7ac45b286d8322a6fb444a32baa380e6bcb9bb67a8a372e0f7
- TakerPaymentSpent: c38b9054831ebdf8b58a94ae81ce428b5bdc4140720143e84a55235935503f8b
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.