why2 reasons
mandatedestination_not_allowed
op 0 pays GD6UYE5PKTD4YHSEV6NJD4R5YH2HDVKB5PNE6AQQFY6YJSMSKBEVMLM2, which is not in the allowlist
counterpartycounterparty_denied
GD6UYE5PKTD4YHSEV6NJD4R5YH2HDVKB5PNE6AQQFY6YJSMSKBEVMLM2 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
- a7661de2533c24122ab9f8af1177b278ac81037e4730ca477baa78e68222c7e2
- request
- 85772d6b735434599bf8adb743898bdb2e87479ee128301a14eefa1c8b80c032
- transaction
- 931fd8aeba7f10a1e14a1fd8008015d56045978acc65f964f102611317f51fbdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2636
the chainentry 2636
- sealed to the entry before
- 1fd012f92e9b402b6a81ecdb26cd6a7318c9c21fcec88f461489563ce3614c1c
- this leaf
- 17a7bc6ae50bdce63561006ddce1d3c6fc41f11ee2aa73679ebc4431ef39abd4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mxWfSDFPVyyZ2BRchlidt4XMU/jwsFBks8AByZunuVgDX3EH0yD+T9q5PFaFT85U9QHUTFvynJ1XiMse1GS2BQ==