why2 reasons
mandatedestination_not_allowed
op 0 pays GBYAT5VWSUD2DFV4Q2MMP7CX7VCTEQEQMH7THFXU4Y7O4SKC7SDD7XEB, which is not in the allowlist
counterpartycounterparty_denied
GBYAT5VWSUD2DFV4Q2MMP7CX7VCTEQEQMH7THFXU4Y7O4SKC7SDD7XEB 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
- 463f85904baa6f8f820bc42c5fd22b5c677414fb3a477956a7772fa2b9392e69
- request
- d1c481887d0d9446870a7f0bb5b1a46cf5053f36f6f4dd9991a2492e023ee611
- transaction
- 865f9e5381d08a5be88a45b25ff35cb9b8bdc16825cf05238737983c0fe7511ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70222
the chainentry 70222
- sealed to the entry before
- 09d2a3aaf63bc75e5d014f98fa166834ea09ba6d5492f50deeec9f369bbf1c73
- this leaf
- 325695c013b04d8fcf4845489c9e3b5f45e346832ac6bd341f302b19d3687a50
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1pYJ4UX5src9dgWYIoTtWtiBdlsulzyZIVEwknGxlA5R1/tB/k0V9GHPrc5ZzGBBa/pKx0a7gwdzMVWc1IqOBA==