why2 reasons
mandatedestination_not_allowed
op 0 pays GDK2MOQBV2ALSUXEXMWZJAT3FQ7YFTZ5D3ZRQKLDLIWOIKYHFYLZUFGD, which is not in the allowlist
counterpartycounterparty_denied
GDK2MOQBV2ALSUXEXMWZJAT3FQ7YFTZ5D3ZRQKLDLIWOIKYHFYLZUFGD 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
- cfe4991cb53ebe88e8b6325b5dbf9f06e7a1792bfc19d71663de7db7fcde4274
- request
- 184c898d8ca4af1bdfa956f6712b7588bcdc168928abc3a3170433ebfe96b238
- transaction
- 75aa5e85b650d62fbaf406c17330cf3e72ea351960e8ccdce500aceb63dabd8ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55699
the chainentry 55699
- sealed to the entry before
- 0bbd870c972b49eeff465493f83a80f0974054ebb3d48711dfc3bc64dcf2e581
- this leaf
- 62865d326148251b02d7e917a07296c972b025f4baad4d1f10897b4f7ddd3350
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Va37ZLudSi1cfOEc8tT1XareaRjixHduXBzr6ZGWALS+TFFzYELxFFQb2AwiNDpkDuqzTLmNy1u58T+4cPsiBQ==