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.
b57957da80cfe5f28186cf3d3681719e0d650d36333696fd351280ad7ac8d4d0
Both payments are on their chains and locked to the same secret hash 2b2c388112ef8643cafcb6666e4da3a2ef5b7c6f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b57957da80cfe5f28186cf3d3681719e0d650d36333696fd351280ad7ac8d4d0
- MakerPaymentSpent: ee0830d22a97c110e71aaa6177dd2ad737ec2aa7c97937b285bd9880e53d59a2
bf96d421c988fada538e8d545191947bc49a5d56e981c6f3151a32fe5f86d33f
Both payments are on their chains and locked to the same secret hash 2b2c388112ef8643cafcb6666e4da3a2ef5b7c6f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f93dceb71d6b57efbf4cfe1be087082e6d2a90334cd45665bbb80ef8b35b76d0
- TakerPaymentSent · TakerPaymentReceived: bf96d421c988fada538e8d545191947bc49a5d56e981c6f3151a32fe5f86d33f
- TakerPaymentSpent: cf779c24a2847068d6d05844fd9850b0335f5693b4bf92775a24ee0be5accd7e
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.