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.
f731740dbbf352c270ceb14aea66ed286856a46684d1820e450df9f4fafc2634
Both payments are on their chains and locked to the same secret hash 377fb3076250f034adf2766c47c46ebe378b8213, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f731740dbbf352c270ceb14aea66ed286856a46684d1820e450df9f4fafc2634
- MakerPaymentSpent: 7400b13488d8c1e1d97bf4f4e2d58e6253466bb6f3740fb2c31d8db8fb20d79f
23e46523c14f5f88baf70365e0134cd0a34685dd9de65184c709249919971a8a
Both payments are on their chains and locked to the same secret hash 377fb3076250f034adf2766c47c46ebe378b8213, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 008a2a315d796dd4fee8bc9bc5446f53e70d89ec9370543e1afbbe13750ec8ed
- TakerPaymentSent · TakerPaymentReceived: 23e46523c14f5f88baf70365e0134cd0a34685dd9de65184c709249919971a8a
- TakerPaymentSpent: c5ce8343bc8042c25e76a22df3c1fa52b7b368457616f337241ecdf51a05541b
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.