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.
4b9f601437380c2a324f51d5d94e4edd5efac4d73cd768801ba3c26d5557f73b
Both payments are on their chains and locked to the same secret hash bc9a6ebd88dc43b88dcd5dfbdc31f2e664e52730, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 4b9f601437380c2a324f51d5d94e4edd5efac4d73cd768801ba3c26d5557f73b
- MakerPaymentSpent: 9dbbca371ee68bca5173b1570352eaa0292395cdf87264a67d6185cbc49c56c4
efd2818d4b69c707e9f8a36539f0c7439daf8e32a589b20a97608c1bcc611ec2
Both payments are on their chains and locked to the same secret hash bc9a6ebd88dc43b88dcd5dfbdc31f2e664e52730, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1fc4db30344031edbc424a9ea49222351ffe208b117778f33b5675df7f79fb7c
- TakerPaymentSent · TakerPaymentReceived: efd2818d4b69c707e9f8a36539f0c7439daf8e32a589b20a97608c1bcc611ec2
- TakerPaymentSpent: 8588b49da8e0c6ebbf33d40c33211655d73072a55f20bd588314c63af4cd1a4d
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.