why2 reasons
mandatedestination_not_allowed
op 0 pays GDN3U5RPS4HVZOVLQH6IX6FUNQDVBHQ43XWLZYJOOIR4JTLMTWZWNISZ, which is not in the allowlist
counterpartycounterparty_denied
GDN3U5RPS4HVZOVLQH6IX6FUNQDVBHQ43XWLZYJOOIR4JTLMTWZWNISZ 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
- fcdf457e0f8e803fe5cee96a09f7ce44122ca10a2e666878cd9cb0c77d3732e7
- request
- 7c378b3f748fe6ed9332ba9dae028ad9810c228f2d6c9e27328872736d632f1d
- transaction
- 4df8529a097b61d4106ad0752843988b1f587df2eb122b83ca018114b3ad4225computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10579
the chainentry 10579
- sealed to the entry before
- 0b04fbc7115a5c03859f553e655456f0caee6630a0eb3cbc6cab08a3fc39e3c6
- this leaf
- 2d7f5ae8c6411efb819989368c57acd593dfd9762bbc25337a253df3742cef02
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K3zSH+VflHII9qfm07DkRNVGueW3nXfljiI+1v7+vPCnsoJjGMB8rnuFenJYdnTQzbgzN4PA1NQqsIeebrV/DA==