why2 reasons
mandatedestination_not_allowed
op 0 pays GDAT6XINAWAPR5MOCE7S25KHDTZBNCX4ZAAPSZ6GYAKKKAH43ZRCBIJG, which is not in the allowlist
counterpartycounterparty_denied
GDAT6XINAWAPR5MOCE7S25KHDTZBNCX4ZAAPSZ6GYAKKKAH43ZRCBIJG 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
- 93aae5c21d39d12ae58714d8a9279fa2cf4015f466b9f6bbe531bd81fb2a9c67
- request
- 8a680e288343a5e6d224f36e2778a4149b2669080e6b9395fd93761a66c6132a
- transaction
- fb298ea8d38e6dbb1602a8066f85f295505834bbd98d2396a80edea3818a447acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43103
the chainentry 43103
- sealed to the entry before
- cfde94b2e843030985e98f7f95a8371a79750f9e5a5cb9e5ce4fb4edeae5394b
- this leaf
- b2e79f02c24faa78f02a071ab201b1dddcfcd7c147bff2556d3b9e06def3c245
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dOzED7szENur+W83416p6MzdMODqkI4FsMGR+v7Ix3MeqYXbXYdIpnb0mgw1f6xS9EeOoMU8upf17tEVJmPoAA==