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.
7be05c281f3fdbb25242852001a4e2aa685faf672fd346e7af002fa62d96a985
Both payments are on their chains and locked to the same secret hash 1255dfd66bc7c3ed8fe7fca33d467e25f44d36c4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7be05c281f3fdbb25242852001a4e2aa685faf672fd346e7af002fa62d96a985
- MakerPaymentSpent: 3bc1359418cb26691989745a320be04759983bf2b936a9e97adfbd68ce2a0a76
6b2064334cc9022ba58cfc66b7518bcb1fca47ab6a4cfd123765205c3ec5a111
Both payments are on their chains and locked to the same secret hash 1255dfd66bc7c3ed8fe7fca33d467e25f44d36c4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8a0ef53f3a2573a8297376dec0e63a51b8b68708ad8e145c0020aa464827aa99
- TakerPaymentSent · TakerPaymentReceived: 6b2064334cc9022ba58cfc66b7518bcb1fca47ab6a4cfd123765205c3ec5a111
- TakerPaymentSpent: b82ef881373498539b557c7045493a5afd7dd99b1954dab1928b9ebcd9cb0332
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.