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.
11fda30a5d661ae9aef6c267696ea02566bbdea5d71719ad5b471b8bccc8b07b
Both payments are on their chains and locked to the same secret hash 8f112adb7821f24f533acd5a41edb00fd7c4a136, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 11fda30a5d661ae9aef6c267696ea02566bbdea5d71719ad5b471b8bccc8b07b
- MakerPaymentSpent: 4247b52809f46348a655d41bc3caa28a271b0b02f279a3bf3244c9e6767608ee
760ce70b5a2b704be7b02ff8f55e89d77d1d1e72f285000bca5fd3de8362b13b
Both payments are on their chains and locked to the same secret hash 8f112adb7821f24f533acd5a41edb00fd7c4a136, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a88bc5b4e1311f79eb8a2e56191befeab3c9bbedab7e81a02f338d8662b284f3
- TakerPaymentSent · TakerPaymentReceived: 760ce70b5a2b704be7b02ff8f55e89d77d1d1e72f285000bca5fd3de8362b13b
- TakerPaymentSpent: 9fcf7722889d8c0c7113cce9cea2fc40a504897a89d81854d233308166ab2bd3
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.