why2 reasons
mandatedestination_not_allowed
op 0 pays GBQSMWQUBNCIO65ZZPZU4VFVDYO4C3VBNXRJKFNHD4S7JXC6ZO5VN4X7, which is not in the allowlist
counterpartycounterparty_denied
GBQSMWQUBNCIO65ZZPZU4VFVDYO4C3VBNXRJKFNHD4S7JXC6ZO5VN4X7 is on the screening list: you placed this account on the screening list for this run
what it was decided fromfingerprints
- rule compiled from it
- 610e401c691af4e8b8cc919e7cdc8b22b44b54c7f987b9e53780f21328f2f503
- request
- 2a358c7a1f7c0f8ea78ce5cdb8f52e25eadeffa092e4f658620b2b27488232a5
- transaction
- 8fddfcfbf055375c547a9a58bb441fd7a6ac06f49a00b7fb9e6309d7d75c6bb8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35342
the chainentry 35342
- sealed to the entry before
- df1ba7787609728f12ed77667be0c133ec050f44cbab4364444a91eda8424e90
- this leaf
- 2f9b97eb4bad920e3ac2a4f95b0313c7b7b70225a3e928d7ccf95010aad447a7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uByELnKGOrAMsOFvISxT+fyIVAIwHr4HPceGwhXca8SSI8CE3odSsknrHo7rcgVJKuIzn3ZzH/tE22Q2s1oRCw==