why2 reasons
mandatedestination_not_allowed
op 0 pays GDYNYXP4NOXJK76MCUWKQESCZ4VNXY3IGXZRQGJBWLSQQWXUOHMJP4W7, which is not in the allowlist
counterpartycounterparty_denied
GDYNYXP4NOXJK76MCUWKQESCZ4VNXY3IGXZRQGJBWLSQQWXUOHMJP4W7 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
- 8279c08a13b67afc35730c18aaf65db59f53004802f8d2468322948af3c91b27
- request
- f2adc59e820e62f81efbeb8b371b2e86f86ea71fc2e0c2331c7cc4637f7548bc
- transaction
- d5ec5f116c680c69157c0920aac153cd2f5e0ee50af2dddced28a2a7460eaef1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39006
the chainentry 39006
- sealed to the entry before
- 5c2308dc0d5eb8420cc2edcde1439d17bc689984eddf167bbb477012f2ad029b
- this leaf
- bbed25ca463b0513d3ff0f88872b23dfa8160a8a5713687da5a1497d70af6efe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b94Sosk7MhNyXINlJmhN6vIV1TGo/NFP4UwCETeZmqWG7ob05GfCcgRAnBEB787WI9v2/XtyTMWg+l/vQ6osDA==