why2 reasons
mandatedestination_not_allowed
op 0 pays GD54DYL6U2HMU554GC4P74GKW542SJKY2ZT3NBLVQU2P3KALHNSWFKD4, which is not in the allowlist
counterpartycounterparty_denied
GD54DYL6U2HMU554GC4P74GKW542SJKY2ZT3NBLVQU2P3KALHNSWFKD4 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
- fd5eb8d0f583cdd238874058752d591504ffdfffaec4dc47e2b2b871f891da9f
- request
- 4f616eae6764f0b3ae20fc4f25fa0cfb89aa81bf38c469985634cd3065b492aa
- transaction
- d06a4806c5ec58d7eb4bd2b827178a213c8ca7d202c74b249e6c6a4ad456c8d1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67
the chainentry 67
- sealed to the entry before
- 07f250fcda023ca6e10879a4d29c4b199cf69ed5d9b2fd20dba035c99539569d
- this leaf
- 9e967907a9c1f3d8f9bf87768fe37c62b82fecb58520fa9de23167ea800083b6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- x6fCo6fE1QV1hX6+e+PcKiH61p3h1yLnsJY+ur5CZDu07O3eCiuO9mIzWCd9ZxF3iOvE9cgBUmfXNjLI2p9fCA==