why2 reasons
mandatedestination_not_allowed
op 0 pays GBDZVXQNBXLO2DUCDRPPYBU3RJZ4FXOGMK36M5NEAZF4P7GXD3STLD2G, which is not in the allowlist
counterpartycounterparty_denied
GBDZVXQNBXLO2DUCDRPPYBU3RJZ4FXOGMK36M5NEAZF4P7GXD3STLD2G 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
- 6a8d65edeb9c5225bb3d30bac7910b9c98f7f07d8c86c2942ad76e4653527d58
- request
- 2e3f7d6e54c4dc523575b119258c2eb64074980cce26e2f080f5ecfc9acf35cb
- transaction
- 0e415eb18b91b433c9a73dbecbcc331c2fa63e6527cffc0dbea0983a5509e778computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37960
the chainentry 37960
- sealed to the entry before
- 05c886a30ddd205a3df7e4cbddc5957e582cb139fed0a6bbf2a89a1929a620e9
- this leaf
- 1d41eb0a6788a947944dc3b691097b03a25d4d86bf4c80fc842214acb41ec98c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- t3YLmUT29A6P2B7ZU9KOrYIRK+iHSrNg2NM7/UXX7S8ITNonQbAn70fpyu0jES0WHf8nU9ioV/WBDmuJ9lPiDA==