why2 reasons
mandatedestination_not_allowed
op 0 pays GDHOMTHA4JAXJJ7BXA56LQFXU3FWW56IDQ2ZOBXK5GMDRUXHX5FJNKLR, which is not in the allowlist
counterpartycounterparty_denied
GDHOMTHA4JAXJJ7BXA56LQFXU3FWW56IDQ2ZOBXK5GMDRUXHX5FJNKLR 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
- f2f361c45cf162f508295d59dc238af6bffbb7352f3b181ef7c2a1ca821aeabb
- request
- 7209c2477ad18ba6b6b85c547658de356a3db24fb218f06ea41d9d9785192078
- transaction
- 21f777a420527e340296112fe1329b1d10f3d7d531a7f0a9572ff0765ba50019computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47061
the chainentry 47061
- sealed to the entry before
- bbedeb50939bec123b8bd2c6504d314236f9cea20d024c7e2e0c3ccc76543baf
- this leaf
- f8b25e231dd32e9def223fcda5643f728dc560ef25ab3b79a7b9156dade8205a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8zrx6Bswt089nYGj3kFVla/LDZUoYlmQJXYyP7RF4dIu6iZgbpGRh9OPam7QLYfUGsU3XjzvTS0U1dS1KkytBQ==