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.
fd3e71066928c961ad56b52a3f315ae2e99349f97af912da7fd488b47b621474
Both payments are on their chains and locked to the same secret hash a226d4f51aa589558fc04cd5b93acce0e59a74a6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: fd3e71066928c961ad56b52a3f315ae2e99349f97af912da7fd488b47b621474
- MakerPaymentSpent: 93ae02935539a8bc7c21834e07d9d906c4db8dc8ad794ae89b9f7182b4fbd4e5
c4bf6d0b2c8e55ae5f44aabf872cd31908cc0ed48322d34d24d04e07a4073ade
Both payments are on their chains and locked to the same secret hash a226d4f51aa589558fc04cd5b93acce0e59a74a6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 955451f4d89c8323ee5f50e746c71cd1594afa375b29afd500b403d0134fdd2d
- TakerPaymentSent · TakerPaymentReceived: c4bf6d0b2c8e55ae5f44aabf872cd31908cc0ed48322d34d24d04e07a4073ade
- TakerPaymentSpent: 2aaf2fe22e6dfabb9f110b1dd03964d2f04a795638099487f0e9a6dff6c86413
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.