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.
5a305a4a3d6eb10c35ca2c5c35f104428547c6baccf55185ea904cb5d8e7fbd6
Both payments are on their chains and locked to the same secret hash 4d2e0224a18a48be0e49ea1af0004bc37bca5d9d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5a305a4a3d6eb10c35ca2c5c35f104428547c6baccf55185ea904cb5d8e7fbd6
- MakerPaymentSpent: 305e12bc3f3c888cfd0d245889973c2748bcf36375a774c8600ea3ff73143d6d
d7ddddaf25d7228a534ef3bfc77c3537101fffe9ae7ec1bd93fe0ae5947c7e49
Both payments are on their chains and locked to the same secret hash 4d2e0224a18a48be0e49ea1af0004bc37bca5d9d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3cd0600c3b1ca1c3a1c451b4db01beb84ea15a64eca7d213f7ebb0cff31d09c0
- TakerPaymentSent · TakerPaymentReceived: d7ddddaf25d7228a534ef3bfc77c3537101fffe9ae7ec1bd93fe0ae5947c7e49
- TakerPaymentSpent: 3b54f30b8668680c6084664a290a450cbe4d0c1376abc97df4b0faa072e39010
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.