why2 reasons
mandatedestination_not_allowed
op 0 pays GB63XJ43VEZ534LNK2Q2FOWMDG74FMPCREDY7EGEHMRUJKOX2ZJ6AEAQ, which is not in the allowlist
counterpartycounterparty_denied
GB63XJ43VEZ534LNK2Q2FOWMDG74FMPCREDY7EGEHMRUJKOX2ZJ6AEAQ 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
- e2194134dda008c25e2647593267a788d2f8b1dafc362b8436dded4c6761ce57
- request
- b180d390fc9d0564748bdde53a4a031d62f9fef83a2f0b86e7c19b971adc4b44
- transaction
- cc7f9bd909c912e0ca634b7c281a6347afd966721b98bc9202c90630d53ac232computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62614
the chainentry 62614
- sealed to the entry before
- 87c4cda44befe054569a5f9601c0d9199323e5b3218e1a1d2e1d4a96e981919f
- this leaf
- c8432afe3a147a11633eb06546957cd4796da544b16570e59445394b8066a364
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Lw+fgLlG3X5UdAkVSPB16uiN6D+ouLe3ydvCixZxc7FSnfyGD4gQUCUF5Mx/5UCALbJz4iWv0SU5R0g8dCXNAg==