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.
1e5fa27c8b4ebf4d2157f03e28d147c6bdfda8e42b6aeac58e129fd6686bbb6b
Both payments are on their chains and locked to the same secret hash 9a6878f7ce6df47e7690d425c630cc5634f1f6e2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 1e5fa27c8b4ebf4d2157f03e28d147c6bdfda8e42b6aeac58e129fd6686bbb6b
- MakerPaymentSpent: 4088787fa6fa8e837adbfd31d744f5390e3ed7f248804a9feaa7f844574f7005
46b14882012047dd9b80cce4657af2a357325a6b265bd05bd0c12f6108f92242
Both payments are on their chains and locked to the same secret hash 9a6878f7ce6df47e7690d425c630cc5634f1f6e2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b56360be2e23b63253ac2b2af1e34b63e2a4e942ba8bb72583113991b8d1155d
- TakerPaymentSent · TakerPaymentReceived: 46b14882012047dd9b80cce4657af2a357325a6b265bd05bd0c12f6108f92242
- TakerPaymentSpent: 8bd9787b5c1cc48f81f3426dccdc655a3366dbff6eaf8ff7e943290b2cabdca1
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.