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.
c36ff8d9b45966596294042fc5a91cab8a19d1eda809954651a7df98b280bfea
Both payments are on their chains and locked to the same secret hash a02243b624492b6dcb8483e08000acacfbc50905, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c36ff8d9b45966596294042fc5a91cab8a19d1eda809954651a7df98b280bfea
- MakerPaymentSpent: cf96900617d1d0779e34fa1d008f81dcffcd1ca8c0db60f917cf3db97da2ce74
817f434f00a37e6256ed7434017f79b01ac6caf8a5682fe63804b34311912481
Both payments are on their chains and locked to the same secret hash a02243b624492b6dcb8483e08000acacfbc50905, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 94b90fa57da1a0974634a34c9d8c559039e76950c5c7f2daa155a87ef3609760
- TakerPaymentSent · TakerPaymentReceived: 817f434f00a37e6256ed7434017f79b01ac6caf8a5682fe63804b34311912481
- TakerPaymentSpent: 6cc7d3a6c02543c9accec972cbd8d98c81cf17bd022d04675322745bae37ce89
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.