why2 reasons
mandatedestination_not_allowed
op 0 pays GDTD3VTKPY3KLSPITHZLMJPFRGO3BHLA72DSLQGGJG3P4QBUVPD2P4AQ, which is not in the allowlist
counterpartycounterparty_denied
GDTD3VTKPY3KLSPITHZLMJPFRGO3BHLA72DSLQGGJG3P4QBUVPD2P4AQ 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
- 3e3e474f51084f665b3372a5badc014748da9fdaf207b5315e3d1f206a5d4aab
- request
- 234ad14387841168c0b5610f90121b2d6f747b2f607fcacbdf643ae511e2f315
- transaction
- 2633ea9512cb07dacfaedb6f9dd23f146ed8a0976422b8f9dc5776a61f3c0643computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 97
the chainentry 97
- sealed to the entry before
- b2f5a9258f4c5bf280884f54033f7b48bba3946b6a85fb9e8241b222b66d5327
- this leaf
- 8fa39b3c74bebd84d523094cb94930bf5dc82910f7abd4796992965cef92e8fc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Xi4KZEz83AXWr7bDx8eLHhaM0YmUb02HKajdpAMLUaeJTXbFpwBeR/DXZlugf/7hTjnWV0guQDU64AjghLoQDw==