why2 reasons
mandatedestination_not_allowed
op 0 pays GD5KBLXG3IULRLQ3P64BNJEMADJA7NKSXJEW24DQWBSZ23ZET35KMPJR, which is not in the allowlist
counterpartycounterparty_denied
GD5KBLXG3IULRLQ3P64BNJEMADJA7NKSXJEW24DQWBSZ23ZET35KMPJR 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
- 9e0625824749ff7657a7d95f18cf9eb2b8f22b6a623e7cbc0350b8a2b2ea5532
- request
- 246f5f343c95a06995b2e61f5cf0beecdb659434303307bdadc24f8fbac30cb5
- transaction
- 69d4d085e0125b6226332d5652da83cbd8f2dbb8a4f1331edad3509e82ef5853computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60692
the chainentry 60692
- sealed to the entry before
- 4d6d6ce4beafddbefde734fe83a45999fcdeda1d09aa8981dfb7f65718424c01
- this leaf
- cfb8b525cfa456a5f3f80d62408753b9ef8ae2010fe2ae99a1c9382698da986b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vgoOJetm5l59MqqO0KGsFTHIFZCr5VLqeFlcZH9hbWm5X65OgUI09E4amjOivnjDYmI+lv9oy5rsefCab1HQAw==