why2 reasons
mandatedestination_not_allowed
op 0 pays GDPF6O4YWHCLV6MVEM2EZG2LYZSFIMDU3HOOBQEZBUZ6CJWQHZ3NC2JN, which is not in the allowlist
counterpartycounterparty_denied
GDPF6O4YWHCLV6MVEM2EZG2LYZSFIMDU3HOOBQEZBUZ6CJWQHZ3NC2JN 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
- 6620595f943e316bdc248c2244852612f2186bd4b9ec6cd3d46104131d501440
- request
- 07916c50b98bbb63b282bc4d8cf841576fa5fe7ad8e1ebadfa3fd5d7a113ea83
- transaction
- 2fc58b65bf48f9c403d8dbc502e8a68e8d5e11da119ae3b5a55469b784071a3ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64461
the chainentry 64461
- sealed to the entry before
- 95ddc6a708eb3a94b3948840f27853b61894e9c33b78becd9ce02ff4876a983b
- this leaf
- 361e9c562bab6ca0fcbf413ebd26db08394d7e7c681b56908b94719ad6e5b697
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eMlyXk/7ampsJzXn9hbxzVlCdNHtdSivGhVfIPns7xihTPH7dD8GyypyYpdHBmCSfd+KYt3siUD1/835Gt/sBg==