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.
311bea7e59f13bb62ccb197da3cd99d7a29fc61b132fadc90ce4a0db676f19b1
Both payments are on their chains and locked to the same secret hash 626350e0032a958250f839af6a769a96e4a75943, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 311bea7e59f13bb62ccb197da3cd99d7a29fc61b132fadc90ce4a0db676f19b1
- MakerPaymentSpent: 23769310551aacca716e425a065b4e69503729a87919aeaf5f5d41fbee228979
a0a9618dfdc3e913a279de4510cacfcb61814f335c6ebaacfdf3ffec1afa782f
Both payments are on their chains and locked to the same secret hash 626350e0032a958250f839af6a769a96e4a75943, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 608b6f8b3d941c47af38e3f85be8194418b0ad9c95a3c90ae63adb78676a973e
- TakerPaymentSent · TakerPaymentReceived: a0a9618dfdc3e913a279de4510cacfcb61814f335c6ebaacfdf3ffec1afa782f
- TakerPaymentSpent: 929d39e3726c2ec6367a9bd68918574096e904f717289678c73804185c75a0a6
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.