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.
4cc4505fc61ab7a8be613011c72c59004a38b1670677f5af2b72c6fe30ae9a04
Both payments are on their chains and locked to the same secret hash ca73e01e3829c80058ad1b12fbecc3c675ca072f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4cc4505fc61ab7a8be613011c72c59004a38b1670677f5af2b72c6fe30ae9a04
- MakerPaymentSpent: 3699e218e591da6faadb4be272fdf5f49d602a3789be9d575a683b0f4c8a8b4b
8bb51ff02068d072c906e07cf620d3dd73168b610b91efd5b2c0b6728d7f4df2
Both payments are on their chains and locked to the same secret hash ca73e01e3829c80058ad1b12fbecc3c675ca072f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: aa7aa14abd1e9ed667c83f0bd4a323dd12e76e0080b8cdc33a36f01fb30518e4
- TakerPaymentReceived · TakerPaymentSent: 8bb51ff02068d072c906e07cf620d3dd73168b610b91efd5b2c0b6728d7f4df2
- TakerPaymentSpent: ce78d579a6b5fffb4e09be45de58e533215d8e5a4ddaa1bef0e016bdee92cb62
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.