why2 reasons
mandatedestination_not_allowed
op 0 pays GDUQP76VMIZHYI634BEM4WRO4CTGVZWYR5DNQDX4WB3GHR6WGYEPVGEO, which is not in the allowlist
counterpartycounterparty_denied
GDUQP76VMIZHYI634BEM4WRO4CTGVZWYR5DNQDX4WB3GHR6WGYEPVGEO 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
- d2860b142381b53b8dbe16671fdb99f940bc8d809d009d6bf84e2dca7a370473
- request
- 1db810164e48c542b720f86b4b9d1d5b7cfb6fd38b7f0d1304cdd1789939a9b9
- transaction
- a68a65b471b3021f2bea2683de0e58d946ec5397a08ca279daa99ff52d9ca468computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11550
the chainentry 11550
- sealed to the entry before
- 7a14eab96532fd6857cecd6f6e12a1c77fa1a91acbf573b4e56c85b1e81b84c5
- this leaf
- 4a19209c1e5f29331ea678dea8d56edad4c2856edce30e19512b4e672722d89e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /YTMPDj+M5IFnfph0bESeRDj1xmwv5CuX0c5n9E+Cmm1grNIfrnKBNUIREgjkqG0UMZvrknchdOD4WnBGf/NAA==