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.
a141072db1aa395e0733bb47f84a8e909f9917c3e6a0e242ef5cdb584bf0fa7c
Both payments are on their chains and locked to the same secret hash 6b978a76cec505c1f12543efc56307df7094790b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a141072db1aa395e0733bb47f84a8e909f9917c3e6a0e242ef5cdb584bf0fa7c
- MakerPaymentSpent: 393478f7c6e0d1a80d3278a38444b0b527c327a3b0c570963c2e945995feb8ac
4305fccee82767bb8711547fe9483244f77193b4a7ab30e53151908eca2b9712
Both payments are on their chains and locked to the same secret hash 6b978a76cec505c1f12543efc56307df7094790b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 161d757ba611bef1f0bed008c64eb05315bdcecb9a2d6f396077bad39f51a9eb
- TakerPaymentSent · TakerPaymentReceived: 4305fccee82767bb8711547fe9483244f77193b4a7ab30e53151908eca2b9712
- TakerPaymentSpent: 5d8cfaa06ca052fd8b83e09277deef745457d4d1560cb583316c9ee7e9aa2f7c
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.