why2 reasons
mandatedestination_not_allowed
op 0 pays GD4HYIDXRAW7EWJQXLFNNV6CFN4TOBSOOVC2PTWBX5QP5CNLPWI2FHO2, which is not in the allowlist
counterpartycounterparty_denied
GD4HYIDXRAW7EWJQXLFNNV6CFN4TOBSOOVC2PTWBX5QP5CNLPWI2FHO2 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
- d9a562625deb5b6ed917743d3362a6ede84107c7b61c3e32c74bca6c6b767fb3
- request
- 799c55b1c290dee403cec5d4a895ed48ef13855f8a67178a9d0ef92986ae4683
- transaction
- b7c8938de2a4d07e79c4ca4b5a40b1d295b6cc4d543b567c6e8c23b449beb942computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63440
the chainentry 63440
- sealed to the entry before
- b89e0849e7314c97c32f73bb65c16fa81c1cd9dc849de647e0b2ad410d285dbf
- this leaf
- bcca2daa2cdb10e61d5983d67f4eb1d738f0d7d627b299594f7a26fb6745daf8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JBUnvG4mMkjdXYci3zzJ7YJGreWfZkE2vyQp6uUR2GAguhcKbOaYZA4CZ64p10woiJ5qvwbH6akD374zhiWoCA==