why2 reasons
mandatedestination_not_allowed
op 0 pays GBGF3WLE7BXLX6I5WZOU7BL4B3C6AOEQ4I44A7JTVJZD5IQ766VIXF73, which is not in the allowlist
counterpartycounterparty_denied
GBGF3WLE7BXLX6I5WZOU7BL4B3C6AOEQ4I44A7JTVJZD5IQ766VIXF73 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
- dba5e811e69bfb8c1bd2022fea4bf2046e857bf1b7f6e807b017abc274b00e1c
- request
- e9be45158e4e935edd8c2636b82a2f7eb7a99182d3ac4c2ba228c439f1395527
- transaction
- 498a29e35cbd26f498496a41eb71c5884cafa8757b34d310ba7dea714bdc3f9acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35743
the chainentry 35743
- sealed to the entry before
- 25186a5c6f6791557aa42e491acbb2da08153357aa6bf192fe672bed02499e23
- this leaf
- 1efe76818e7feae70402cfa03dc191b7ed39372493c7d9cff09762a4a5a370de
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5iWUJyy3WCDYxOaGqS7EC3tbCabpReigkmJld2AsyMUIeokBXAI9wZ5tivmadh4cl0laLIEptzUGw1TaJM6jDQ==