why2 reasons
mandatedestination_not_allowed
op 0 pays GD5HYT53EX4ULJLQ2CMY2XWCQPYOE2RHXDGWAQSS76OXN2WMIRGBDRNI, which is not in the allowlist
counterpartycounterparty_denied
GD5HYT53EX4ULJLQ2CMY2XWCQPYOE2RHXDGWAQSS76OXN2WMIRGBDRNI 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
- 15038f434002d8b27823a1bd9152803707ac27700965ff2bf3c53f6fad6159fd
- request
- 27381fe1828a30e02c28061dfffd11ac884539baa99814910ef42bf48661b8aa
- transaction
- a1bc726a2560a70f1343aa18d06ebc91aa28eb7f454b76a6146592a9d17910f1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36924
the chainentry 36924
- sealed to the entry before
- d8cf9f60a5ae25c7659aa73fb5adc00a0e699b1675486aefd06cbe32c8d22783
- this leaf
- 996663666202f3f91e52a7acb0f22341e360fa1d24ca8f2e7d448eeeeb449341
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TD/15lUU3SmkYG26v8pwAbBPUbymSvHtevgJTllIBgjriil8vGjiQRY3TdPHmbPPvRgl7cfYjmDLw4KtM9W3Cw==