why2 reasons
mandatedestination_not_allowed
op 0 pays GDSZ4N6LNIZ3ASDMBB4S57NYO7K43LOM6DRLZYTGUUXBB535RRFMXAO2, which is not in the allowlist
counterpartycounterparty_denied
GDSZ4N6LNIZ3ASDMBB4S57NYO7K43LOM6DRLZYTGUUXBB535RRFMXAO2 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
- f76d490fcfb1b111d85fe2c9c40f92ef54b43c480b20e96dca1920414de34ac5
- request
- c7be7b360c24f61240cc430a2a94b7bb83bd460b40cc2cb78327bc17c84566ad
- transaction
- 6482fdf8f28946f31db28ef56d9899c1d8d78687e0fb63213ca26bbcebec5fcbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2046
the chainentry 2046
- sealed to the entry before
- 91bae1c418b0e558e4044dc379fbcf0ad035c1d46e41b5a308ccf5ab8967547b
- this leaf
- 2839da81e8712002f0f903ce349e9ddbcd0c7ffee1accd3d23d94c5da3c5d483
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vjFn5y4VuYtEybtqUMh0PKbeBVunbPpHaow1UhajwHXUZlkA5sJlYLwEYkxJRJKNo9jCr0sbcNik3uQ9rLqtBQ==