why2 reasons
mandatedestination_not_allowed
op 0 pays GD3NBR4BS72DPLNI47JNYI2SRIFGKZGUF42XY766B3AHIOLBH5VIEWI2, which is not in the allowlist
counterpartycounterparty_denied
GD3NBR4BS72DPLNI47JNYI2SRIFGKZGUF42XY766B3AHIOLBH5VIEWI2 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
- 07dc95ea8dddd16fbaf087863131dbbeb3568382702c5c148a3b9bb05f5e3cdb
- request
- fd94ce50a9001a57600e6e79a5888cfc08ab5807078cfd63802c8f96ee216695
- transaction
- 73457a675e3fc4246d2966de60cb0712b1ce8fc2d68a5d43d5ec018df0397ffccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66204
the chainentry 66204
- sealed to the entry before
- e30deec47f7f8006e5e74c0192ab2c6de053e6348f7bc39869817ae552348a43
- this leaf
- 1d78ebd235d0eff728102fa84b62d7c70a8ac1fc9af748b2e183f29e8ba15a02
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xVlN6cUsh+vzQ5+YrPERehPTV5+h4DENY6HUvTApAinoDzxY4pwjNNxPc/x/4sBBNbciqjVNeIuj+ZBzCCbECQ==