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.
8b2738da6cdb25689ac0a81d3a73e8f8e76ca39cca040ab92d1adda77c7e3006
Both payments are on their chains and locked to the same secret hash 977007af9d2bed1ef627fbad14fb8a92e1448bb0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8b2738da6cdb25689ac0a81d3a73e8f8e76ca39cca040ab92d1adda77c7e3006
- MakerPaymentSpent: 5df1bf452804f5039fe2dddbfc01d240e0c4b2311def2c6dda3ad2b7d25f3004
2920a6a55695a5e9989c330415fa8f6df5d2b7581621fc2ac183b7e50aa20125
Both payments are on their chains and locked to the same secret hash 977007af9d2bed1ef627fbad14fb8a92e1448bb0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d9664ba7492399df16f0d5171e4b3b2e0f549c3872ad4f955586a3342c8d05a5
- TakerPaymentSent · TakerPaymentReceived: 2920a6a55695a5e9989c330415fa8f6df5d2b7581621fc2ac183b7e50aa20125
- TakerPaymentSpent: be5e6f2f37393beb7a94a21b9a2948dd5d2ee3a714fb2ead23e2dfd9ea65e0e7
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.