why2 reasons
mandatedestination_not_allowed
op 0 pays GD3WD7XOHXASMCSLEE5VDBXHO3VXYK5PFFET5S2MTKJELH6G5HH24VLG, which is not in the allowlist
counterpartycounterparty_denied
GD3WD7XOHXASMCSLEE5VDBXHO3VXYK5PFFET5S2MTKJELH6G5HH24VLG 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
- 3d870f8eacbf5e905a43120787ba383b0c0ad654094f8eddcad620b1534d6432
- request
- c7cb2de7697d9bd94f92869c412fd7685e706d7ce9b2d3d376179fe362ca3fcc
- transaction
- 9a0a04fb6dc603c88dae2ca3bacb0033f98a55ca8c1d7efe2441634c5443da44computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39132
the chainentry 39132
- sealed to the entry before
- 46f17bbe4a3e416116641557f8e46c034ec213196d5abecb9bcf73d6d2f7db02
- this leaf
- 3b16d1e0f52dc7a691a0fd8942bb2d4b6a6763e0508bb20245653eb6df3d0617
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GXZhOnrhDv17FoZui3ieQcd0i1FC8YR0vsSRmaA5yDsyNw0kQjdCYMzXZxSxdEK6Z+w5x96mVd+rABe0UpSXCg==