why2 reasons
mandatedestination_not_allowed
op 0 pays GDQWIAVREWAGCRM3KZUT7M76CGL5FQCFVQNVK4KCE5YZ6FWRWGGQHHD5, which is not in the allowlist
counterpartycounterparty_denied
GDQWIAVREWAGCRM3KZUT7M76CGL5FQCFVQNVK4KCE5YZ6FWRWGGQHHD5 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
- 313af61a78da236268dcf3d7c4026c5663cbc63d00398d9c0ef87447f3e569bc
- request
- e6b067559a96500346e9e3502570ef821e0576ea887996da2177663491e3146b
- transaction
- 02b76b34e48c928de6f95fddc25b593746ca113842abe694df8b50523937dd2acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 427
the chainentry 427
- sealed to the entry before
- 40ea785f1cb1148cc1b7529cd01aab88ae7af31eeb3d9ad8e3d97790a5f2791a
- this leaf
- eb0cf591f7b19586ed25eb9c375a77ee9d0b3fa0a881a0c5141766794401c8ee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rgBUc9vUWdX+SJDiCergZajbg9hqM9fVsSJ32ukC7PKUiXSfZ+52mVoT1ttHhkVu29sUMCcgmK8cevTbAKo7BA==