why2 reasons
mandatedestination_not_allowed
op 0 pays GDM7XWKOKK2Q4OFYGJYRYXM5IEKKK5JC3FUJWIACZNRRFSEZTOPC4E2H, which is not in the allowlist
counterpartycounterparty_denied
GDM7XWKOKK2Q4OFYGJYRYXM5IEKKK5JC3FUJWIACZNRRFSEZTOPC4E2H 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
- 420632e1fb42ce1d88a6a7c9e8dfb7685c613e182a602773050365a7dc494015
- request
- 0fd873eb46c2bc143c103e5fbe6d5de11ff0bdd0343c1c569f4288c6b98fe3fa
- transaction
- e0dd8ef6e6f5e2a36dc65db20bac1f3da989d80f30d369c1f3227256322f21f5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26934
the chainentry 26934
- sealed to the entry before
- 52aac25b9e8c761d93bb793a8e3005547d184a160e76d11ec86ce2eb280a3755
- this leaf
- fb0243c497a6d9bc038d77f07cbe2bc6aff941803827a9a92513821ff7e7453d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OIbaCLreiH0uXjRGbIrG47Ah5lajk0wGW6osojiMpZoNC/zM1XX78lN2tWz52nskUSuZIdGrIXU6aYdaBl/RDA==