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.
b18a863ec3821e730a7cec4c5382dd69abf7013fb5d4a461ab2b070959e02329
Both payments are on their chains and locked to the same secret hash 9def1e4f7b0d0bcf3b91b8f2a1b62a1aaa740e4d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b18a863ec3821e730a7cec4c5382dd69abf7013fb5d4a461ab2b070959e02329
- MakerPaymentSpent: df5827c182c2422d2305f74ca5145fe38b271f374da99a6c798ac1f2594f337f
f2a8a56c4d7930a8032c58abfd747230bc94f667b056ee6663a7d909ddb779e4
Both payments are on their chains and locked to the same secret hash 9def1e4f7b0d0bcf3b91b8f2a1b62a1aaa740e4d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 901d96bb63f1f96e90967d3f5de5fd29e5afd5bc93b32bb6340a077721995266
- TakerPaymentSent · TakerPaymentReceived: f2a8a56c4d7930a8032c58abfd747230bc94f667b056ee6663a7d909ddb779e4
- TakerPaymentSpent: e490d7f7363a2cc6639e74bfc2bfd9b0f1447724693571c7093e38e50a40e3de
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.