why2 reasons
mandatedestination_not_allowed
op 0 pays GDLAW5CFZSVWMW2QLSA4P2R3SZKMYYYBFOMGN3SGBTW7AVQZA2SRRXET, which is not in the allowlist
counterpartycounterparty_denied
GDLAW5CFZSVWMW2QLSA4P2R3SZKMYYYBFOMGN3SGBTW7AVQZA2SRRXET 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
- d2887806a63c83ee57daaf04a157302a9360aaa60c8c1e2202a298911272b8f8
- request
- ea85eb792548cccfca7a0f50710fbf790da942358d597f167dd14a8a730aad8f
- transaction
- 7348ee395fe5cfc63d7b7c54dc4e0772bad96431e5826a09f88e524e8b91b652computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48332
the chainentry 48332
- sealed to the entry before
- 2dbfcb279b269e480cd1d5cf04e7baccafebef3ad8c5b1977d5c852622373911
- this leaf
- 2f605f2a38c6d52094b57b43419de7ca343fa8f77ad39edf031ab1b57d63fc5f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AHObK7Z3TLcphYnfyyDLsBjW6kBVCbbt6UrKtoXOkCq8cdmxALW+eqz1mSWtwRnQpJeslVue70T1ySUhaZGHAA==