why2 reasons
mandatedestination_not_allowed
op 0 pays GDOZATCQT7I37DUSU2YWSYPPLSLQHTRXAWXHUGJPY27GZK5IY2A5OW3O, which is not in the allowlist
counterpartycounterparty_denied
GDOZATCQT7I37DUSU2YWSYPPLSLQHTRXAWXHUGJPY27GZK5IY2A5OW3O 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
- 858b1b3d8badbadcfe0b052d8bdf24197b517327f7b9e07366c8857027130630
- request
- dbc267eff46a42d0c7fe9dd6fb717ef5f619213c9203eb08bd01e4db3b26aad7
- transaction
- 63489c113d5143a07d65d5a51e63ef2ff4c62dc98bcd900ae56b04de7c208cfacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41108
the chainentry 41108
- sealed to the entry before
- b3bad0c1036190156b74bdcc5d1de9c3d95efccba0a51c5bdd3558afab9bdd70
- this leaf
- 8d0dde40beebcb5ebcd7dc24047fc75b45e796a6b1598987257d6064ec300ced
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cgdv3kY4oBCgWuHExpaLjOJ1vsV7Uu3mgQsfyBzrLDyN4yD08F/Er/d43shJrrDSPqGtVjNb7Onx3MIaw1vyAQ==