why2 reasons
mandatedestination_not_allowed
op 0 pays GCALQOX3JX4QFJ5QTZBB7UXJSKEFEHAKY2QEJNZAWFQ53IFSF6CUDQ3B, which is not in the allowlist
counterpartycounterparty_denied
GCALQOX3JX4QFJ5QTZBB7UXJSKEFEHAKY2QEJNZAWFQ53IFSF6CUDQ3B 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
- c762932e1a45fd140e113f8dc46081a3500dababb2fd711266ad381bc926f892
- request
- 358b9c675e4868c4d50f4838a1c23ce8a50629ec9af99b02e3c5db4e5c37ea68
- transaction
- 6154767ff3b2be1e0b22510156e9f818f2458f6e08e170acd759fc3544dd9587computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42365
the chainentry 42365
- sealed to the entry before
- 6ed2980cbf2b19d7c8ad207eb57b3fa5c0b511b97d031785694c4633d8047be4
- this leaf
- de50cf07ee97f985442dad3980a08b1a162328a5e44934c3772fe1efa68442d1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KZEpETxPmQksTvetRitYh3ReocDpfJ+HqwmxRCnBrXSretIYLcLOMxeh5judgnddeOXYvA9QOAhg0nqpsAXoAg==