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.
66930bd6a77b359ac7ad493c8dcf28bcbf7b8da32d397a2d7e35ac8d69ab19d5
Both payments are on their chains and locked to the same secret hash eedd2917b8ee95560e48d45139528af78d48d160, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 66930bd6a77b359ac7ad493c8dcf28bcbf7b8da32d397a2d7e35ac8d69ab19d5
- MakerPaymentSpent: 057c2cb46dfe44e38247c4343a23b23cf8c7e9fcc08f3cc75cfcc6058c5cc7ff
0f6a7709f56770c84d1c8055b3c30604972df116a7dd093498756c977285074f
Both payments are on their chains and locked to the same secret hash eedd2917b8ee95560e48d45139528af78d48d160, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 44d9e9bdfeb7747998dd86c8773962ac5766ee634b0f7056414fe16340e49102
- TakerPaymentSent · TakerPaymentReceived: 0f6a7709f56770c84d1c8055b3c30604972df116a7dd093498756c977285074f
- TakerPaymentSpent: 92d630fc56af7454d21e0fd4a6a824f566054998a40d92dd2482810b45052639
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.