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.
36bdaf91427bb4118d905fde2272d3973008ec4c48edd779b05b5d680df9748f
Both payments are on their chains and locked to the same secret hash 38e69374a465fcb4a5c9b50a6ae6d9aa29c839e7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 36bdaf91427bb4118d905fde2272d3973008ec4c48edd779b05b5d680df9748f
- MakerPaymentSpent: ce650bf32264ac253b70c68d3231e4a63c46feceed01dd8e22c59bb85339e2f9
cb22410e517e7997dc76192ad163576f212ecf4fe2f092f2823f12c7d6314af7
Both payments are on their chains and locked to the same secret hash 38e69374a465fcb4a5c9b50a6ae6d9aa29c839e7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: eb675c9dfb6f4a36c47fd81c1e83c9500e820c8aa3f918f8a292e83190639b85
- TakerPaymentReceived · TakerPaymentSent: cb22410e517e7997dc76192ad163576f212ecf4fe2f092f2823f12c7d6314af7
- TakerPaymentSpent: 71de1f48720358a58d38afaa84e0f64d7316d1db82ab06b3db968b11355685d8
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.