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.
0648a0d002c0bedb96a1054aeb695aa921afc29690f79be28c6ac7332ab08949
Both payments are on their chains and locked to the same secret hash 68833875fb3e35835868721a00e0360ffc90e036, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 0648a0d002c0bedb96a1054aeb695aa921afc29690f79be28c6ac7332ab08949
- MakerPaymentSpent: 54213311535338479319bdce0b8931c5f084bc3ced225307938ff7e0aabe6a89
a5255e27b85940db64a8e77ee386e8d8b2b1fa36803fade357f9e6b54f1533ba
Both payments are on their chains and locked to the same secret hash 68833875fb3e35835868721a00e0360ffc90e036, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e0b9e46ba382515fc115fd0163ce15f3cb5a342be3815d9c0a3e95d0d325cf8e
- TakerPaymentSent · TakerPaymentReceived: a5255e27b85940db64a8e77ee386e8d8b2b1fa36803fade357f9e6b54f1533ba
- TakerPaymentSpent: 690570bb755b80f663f58e7c2327a191500d32f6aeb967513fc84fd66c369621
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.