why2 reasons
mandatedestination_not_allowed
op 0 pays GAQSXKH65WSLQN5E7BYJT47XKZGS5SI5F4XWUZQJE2MPLIQ5TTO6EM4Y, which is not in the allowlist
counterpartycounterparty_denied
GAQSXKH65WSLQN5E7BYJT47XKZGS5SI5F4XWUZQJE2MPLIQ5TTO6EM4Y 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
- a94b774ca1600865987f7955034a6696a5392a1c4f5f6fd91a7c9b22525f73a4
- request
- d114a5830adfec28963ed2cfcd4bca1d0abdd06ebcf24792d2fe49615d51e726
- transaction
- 221c79034bf8c0fd5b1d4724bac07f19c308526aa5eec62ca83d65b9d0d1a1eccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73754
the chainentry 73754
- sealed to the entry before
- 4276695c232db99be9d26b1ea163fac8797d4df1fee683c105da10ba0f8709a3
- this leaf
- 5ac2de1e73b98bc5b498a3642987383979546471566c9b438d4338a3bdb0c9e3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MZs8/GmoVzaI7DICbhtJnMyMczrrVUQlkhA+lJsNLm+8N7PnKKHcCVCf4P+c1G8VmtrWT0YZgCDYsovFxYvnBA==