why2 reasons
mandatedestination_not_allowed
op 0 pays GDSNKQFRLENJPTDRTBWXZ4UOKZZ5KUUPMVQ3WLX64J5YEE4FJIAWZ4WN, which is not in the allowlist
counterpartycounterparty_denied
GDSNKQFRLENJPTDRTBWXZ4UOKZZ5KUUPMVQ3WLX64J5YEE4FJIAWZ4WN 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
- bb79bbbbadb6627a0ca9fd9e050cf8da84a5fb1b8fdd5558dbe85400bda0d90d
- request
- e6dd9c77960a9ca05a2a0d045c6fda43226eda3e96342cbb6f19014e0db09a12
- transaction
- 29ac501abb44ab793f4508416756a8a2a4b2cac6d4e5bfc3478acee0ccb19a7ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35801
the chainentry 35801
- sealed to the entry before
- ae8c748a51753bd52dc29b1b9b374c56fe3a0f3fc0a37f4111fea2d807734ee0
- this leaf
- edab8dfebf37a02678f681a90c11acc76769df7bb0af8c2c6d04c98b698d1915
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yXNOSIf+whVyOrC8t+NKC6HaF+bQ+K3snQUbHEWl+j0qnl1ifHNtlEnA0LDFf6ZCQbs970Ri6DzrtJofgfhjDQ==