why2 reasons
mandatedestination_not_allowed
op 0 pays GDDRU3VBNEMF7CT67DYADYERZHN3KZPIMW3PYASJ2MMV7USJAMR22LB5, which is not in the allowlist
counterpartycounterparty_denied
GDDRU3VBNEMF7CT67DYADYERZHN3KZPIMW3PYASJ2MMV7USJAMR22LB5 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
- 157e107e11f147177903bb5929cdb0fb6df58fd628be06282477096bf9f7e9ee
- request
- f42cd6caf12dcf2ffad2511a918395a90c18d0f92ade4606fbb82bb4e99329be
- transaction
- 6ac7f817a7c50e27dd359521bb03be0ba690c4e8d5a73ff477dd5838b9cf8e32computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22930
the chainentry 22930
- sealed to the entry before
- fa38d6a8272885d1d1562791a1117c155955fc2a89a2014d3b73641c9548b0e6
- this leaf
- c32116df97966f145cdea4b22e05dd3beb87eb0759cee232b57e15a1690d98c5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- N7pTa+icuEapIWLYSHc2gj7paO4xQvRpw+rYEnixhXq8Gghb1tbbrJiuDJig0uY+oF/sg5Gqd5+MJdU7hn1jAQ==