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.
7b70ff7e536561ab56506ddf1cfe5ce559d321596d73593e1047fe106dd9a530
Both payments are on their chains and locked to the same secret hash 8985e8d525542f6eb707f387592aec5cf9b28c6f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7b70ff7e536561ab56506ddf1cfe5ce559d321596d73593e1047fe106dd9a530
- MakerPaymentSpent: 3bd5f5a59452f1c10359ac809aaeb3ac640e98836bf4eeccd1a9a31a59239e13
11651e85c15358bc5d01257cff81d1b8c6f3aaf2e718ec227d67584bf66152e2
Both payments are on their chains and locked to the same secret hash 8985e8d525542f6eb707f387592aec5cf9b28c6f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fa4119ff88f6715ba5d5fa3fc455e77f5c76b02db85780be8563d09ef7cd9810
- TakerPaymentSent · TakerPaymentReceived: 11651e85c15358bc5d01257cff81d1b8c6f3aaf2e718ec227d67584bf66152e2
- TakerPaymentSpent: abf45be1ebb43da172bece3e75e0c90633cf6e4637f11f1f21268011f707d4db
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.