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.
736755d4585e651c7aa9afcba5d98b7b4bc514a44ec7b7d5056813ed66491a5a
Both payments are on their chains and locked to the same secret hash 23214933796cf028b50fb580a4a39bd4b3d3383a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 736755d4585e651c7aa9afcba5d98b7b4bc514a44ec7b7d5056813ed66491a5a
- MakerPaymentSpent: 4b9129fb384ffebd9da770706623478bb406b4c30db56d0cb5692ed982e714a0
546b7d3b0ad56a1b03936fdc6d74a4a93afa234e577e6f10187dd3a38c03502f
Both payments are on their chains and locked to the same secret hash 23214933796cf028b50fb580a4a39bd4b3d3383a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 0547942b9fe6adede836797c09df09d77b1a0a03eda45beca83b0e0606a04048
- TakerPaymentSent · TakerPaymentReceived: 546b7d3b0ad56a1b03936fdc6d74a4a93afa234e577e6f10187dd3a38c03502f
- TakerPaymentSpent: b6f7a6ed93063625a64a47100138045859fd3581c05d3935e6b8ce4d27626207
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.