why2 reasons
mandatedestination_not_allowed
op 0 pays GDE3UCOPDLMUA7ZS6C6TGNDIOP2DSECITXMMGDCGRYCELU3CKSWB4H7S, which is not in the allowlist
counterpartycounterparty_denied
GDE3UCOPDLMUA7ZS6C6TGNDIOP2DSECITXMMGDCGRYCELU3CKSWB4H7S 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
- 55665d17ae775713e1da2e3b44ca2f4ea2c575fe84dac038a6cf157d3a5b80af
- request
- 1d0aa436e25c4f54a61d9f640749db8e0c24d744138e736753db122b86e1b76b
- transaction
- 7bce5b1cf563526645237f43d048aaec0453fbf8e962830bd63587b24b90a5d2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11910
the chainentry 11910
- sealed to the entry before
- adb9e24f20b4bc6f043931c75d9b4e457622c3787dad00fa40e635bd35bde012
- this leaf
- 305e9720ab568f5855e20ff447022550d06f8a1c6e83d2067e11856564cbdc6b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xFu4lLhgbrx2Xb12lWM692h7J5jV0biwGy6Fhh6e62fdd+aCFroaLB0D203lCFVwumvZwxSl0uxwrzdiKslQAQ==