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.
01c1ed8b83f4eba80ad24431dc91455208f28997f30f6db77606906ce4b4f70c
Both payments are on their chains and locked to the same secret hash 2cd3c784d49b8b7c714b8d09153d365bb0c6e90e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 01c1ed8b83f4eba80ad24431dc91455208f28997f30f6db77606906ce4b4f70c
- MakerPaymentSpent: 9a4b2c119e5fbb464ea339e020deff57aef068cfc1cd149305fc41af0a3b0518
648d7a7a88d9071eae7358284a0fcb58fa8b1602112e862870f27db1a318c3e0
Both payments are on their chains and locked to the same secret hash 2cd3c784d49b8b7c714b8d09153d365bb0c6e90e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1a5d45d2e338abec1c5675a972eba67a7043d3b5c37ae2ec09090d33fdc97575
- TakerPaymentSent · TakerPaymentReceived: 648d7a7a88d9071eae7358284a0fcb58fa8b1602112e862870f27db1a318c3e0
- TakerPaymentSpent: 3ed58b6a43599e856c50e58e2df28bd620a0230e175dc11986983fbb967f2c91
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.