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.
e62625b5dd6ba2c90c210ecf1de4f9d4449c2eb34f388e014d385a9d4ae8dbab
Both payments are on their chains and locked to the same secret hash 3a86f6ba25f055db5e2a993960a15828bd4ff4f3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e62625b5dd6ba2c90c210ecf1de4f9d4449c2eb34f388e014d385a9d4ae8dbab
- MakerPaymentSpent: 452ba69087718113842c8834610b5f7b5dabe78a9d45f3f2dae537309f58a481
8b5f84a3fb3f30a24a73d074ff208b74889a18b082cc1680bc051b62d34a0fb9
Both payments are on their chains and locked to the same secret hash 3a86f6ba25f055db5e2a993960a15828bd4ff4f3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c8cb53c24ec0efb77a7ff2bf2165da21e89e349291949e6a11fc4814ca38bba0
- TakerPaymentSent · TakerPaymentReceived: 8b5f84a3fb3f30a24a73d074ff208b74889a18b082cc1680bc051b62d34a0fb9
- TakerPaymentSpent: 301180a164e03b31aaa9865b500a844762273c345bd075a58e24ab79d8f85de7
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.