why2 reasons
mandatedestination_not_allowed
op 0 pays GDBR4SHDPUBZH4UDQ6M3NIQVH5T2NH2QLZNYGEKWU6LNNL5SWPKEKPL2, which is not in the allowlist
counterpartycounterparty_denied
GDBR4SHDPUBZH4UDQ6M3NIQVH5T2NH2QLZNYGEKWU6LNNL5SWPKEKPL2 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
- 2d6a8b47d6127b484a1ac31f52ac0a555e26ba1102c84d545913775926860733
- request
- 2d8d409230b7010a60d06fd422821137b98521b2659c8eac716e3706b0c28146
- transaction
- 276bdbd9c83a3ac1316b76f65d5d4de852dce28ac3272712ec2e4a4d834c88dfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28551
the chainentry 28551
- sealed to the entry before
- 38f145370d453205fc836297ec03b996ae9937447e950726f0b67411432ca946
- this leaf
- e050e6af6dad7614357adf8c51a2b18e0d307b85f7fc02e84ea7655394ff3a57
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TzUncQB4UaQ1ul6PTmcHZM9mhPKsJtvX7Q3slS7bs1tEiBNJIX1BLBF3d7kUx8DmB3+wwPMmHQXrKbUgghenDA==