why2 reasons
mandatedestination_not_allowed
op 0 pays GD7MC5SEYEU3LNPVDVAPBWXE4UZ6S2PFZJTK4WM4LXJU6XLVBI5WSAZK, which is not in the allowlist
counterpartycounterparty_denied
GD7MC5SEYEU3LNPVDVAPBWXE4UZ6S2PFZJTK4WM4LXJU6XLVBI5WSAZK 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
- 915742a776da6c1b0aca88ac721b809f3a7b520015b975429faf4e20b38ca882
- request
- 024ce5207eeda75fff8e07c50b4f46f371c71d8fe596fb288f3e824bd8fe567c
- transaction
- e8674a7153188bede30a48d8c925ceb10db681ea855af4e87f3194d4898ea86acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72667
the chainentry 72667
- sealed to the entry before
- 959997d70e6a6121139fd50ccbbf0a17d736bb236a19f3bec5cc70ca359e9f39
- this leaf
- 7445cfad3dbd9988c5ae6169abe33b2804d2497ee4870f3197c3bc9d4b288f0c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- A2sXi7PND3utRygi/eesbDFZreT3D5FdG0CaFs4z9uZzDaV/fbLe4vwuqC22fUjqysSOpCVVRZ1lVliM8h8jAg==