why2 reasons
mandatedestination_not_allowed
op 0 pays GBVUUD4DPSP5KHSMNDM6BZRRRDIFVPXGNYEMOBTS7PUCYEXVDO4OVRUX, which is not in the allowlist
counterpartycounterparty_denied
GBVUUD4DPSP5KHSMNDM6BZRRRDIFVPXGNYEMOBTS7PUCYEXVDO4OVRUX 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
- 64e7a6247057dc740f24870d707d4683f5b01b637cb1daf161879e65854aba8d
- request
- 17d86e4e904ce329ab354d519db6aefdfbede62898230fbe22af3c9fae60d063
- transaction
- d7ebebeb570b9435139da166dc5e6aa7ce08b1aefe57a143642457ae4411c80bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73089
the chainentry 73089
- sealed to the entry before
- 3e56d7a109afd59f7c76f8551d17cb177fd5c0ed194736c79617a0257f6e5e1e
- this leaf
- 30cef8c4ff97bc217a98327fcf0e7c39e9ef89043f65231b0dace2870e72f09a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3Mb+5hOSdY0hHaSvy+cejHeV08jSOy5sry/iBhne5DUj9ISjUSgDNK6MqUaHCV5fQR38XA3MRDmuXk5LlmerAA==