why2 reasons
mandatedestination_not_allowed
op 0 pays GDYNY2C7MEQ2TT2Z3ILYF6VNNS5XZKABE6VASSYGW55GWOHVBH6MEX3U, which is not in the allowlist
counterpartycounterparty_denied
GDYNY2C7MEQ2TT2Z3ILYF6VNNS5XZKABE6VASSYGW55GWOHVBH6MEX3U 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
- 03fbe9fdf8f58bcf5dc028fb45ca7098ad7290e7a295676c534eb892a2fd2cff
- request
- 549c97365ecb72c1337bc28a71e6a004c553ea115d32c6a215638ea58ec0ffd5
- transaction
- e47e76bea2450cae08cd47c09f55f7f46240766d886490af60146e0f95b089cacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59645
the chainentry 59645
- sealed to the entry before
- be34ffe118d5946ad997979765521289ba1539305538af9c897fc15adeaf2cc0
- this leaf
- 90a0a8b08cb18f6a00c9449c98f78d6612c075717968cc8d0c179837d2e416ff
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /76c0C2+5bEmmD4colVXE3pQ7vjwig3zTtMjK8ZeZPXwyCCFMcL5nva6+ufF6RL4IOebDOxXkKos3CvQE0tsCw==