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.
91c2fde0f85f1d1b082936eca4b3fc1c24561339396f5593c621932158c71992
Both payments are on their chains and locked to the same secret hash b6da22a81486576288bb0e2e0b062850a76b38e7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 91c2fde0f85f1d1b082936eca4b3fc1c24561339396f5593c621932158c71992
- MakerPaymentSpent: c93c63434665392df474a3e3a38e12fcba58b7dfb1127c2b7a22a0ab73b95e70
6b940c01f771cc9e0454ab3f21cdbc64ac0d83ccbbd1b0291dddaf921dbd9fb9
Both payments are on their chains and locked to the same secret hash b6da22a81486576288bb0e2e0b062850a76b38e7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f5d528206bdb6fcf36880cb6d924df0d1756c595d6a1926de7a6e9182c9e094e
- TakerPaymentSent · TakerPaymentReceived: 6b940c01f771cc9e0454ab3f21cdbc64ac0d83ccbbd1b0291dddaf921dbd9fb9
- TakerPaymentSpent: f0be4278ee3a0a5065ba6e2112be5ae8eb48de72cb2d63b6dc2b83931ccd74cf
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.