why2 reasons
mandatedestination_not_allowed
op 0 pays GAEDZJXXBNJVLPNAAS3AYCJUCF3URVUT4D3GBA57RQ4NL5SD7TT7GJLB, which is not in the allowlist
counterpartycounterparty_denied
GAEDZJXXBNJVLPNAAS3AYCJUCF3URVUT4D3GBA57RQ4NL5SD7TT7GJLB 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
- 18cf4a261b5f2408c84382dc9c61bba358745cafe3d3a117ba92213ea5a5a502
- request
- c12e0cd4b5738a78b478a949bbfe3055d087a5d8578d289fb72879940baf0179
- transaction
- 3d559c5948ace610ea664f37fe949cf41c22b8a7ac21705ab1a60e33b8d1a62fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34395
the chainentry 34395
- sealed to the entry before
- cecc1b9bef613e83dc424f811b45461449c6311be03a690b3f1f71271b00b5ac
- this leaf
- 19b48f5333e246de0cd5d57bc254176bc97a01e0a808d0d53e09854571267c88
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- j/k8PsiCRiuBiE7gvtL/Fd+P/A4tHPnazASmtREtclVG/3IiwO8Udmfkn7X3WAgmG4CGTz2yGZKVdtCcqARTBQ==