why2 reasons
mandatedestination_not_allowed
op 0 pays GBM44VAOZEFT3BGM3GMZI6WP26VASSBYDMH523TX45R4VHDB4UZSLEOJ, which is not in the allowlist
counterpartycounterparty_denied
GBM44VAOZEFT3BGM3GMZI6WP26VASSBYDMH523TX45R4VHDB4UZSLEOJ 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
- 38a6ffcabe09eb0186622d3fd041977ba88f038239f029ce46fcacfb75dd32e6
- request
- 3c0f08f4b99bb681d3c589f7b2335c3103d3b47871278e10db452aa6825b2989
- transaction
- ae8cdfd0b6efbf963057acb9991ab365a98a7904582c1b70bceac86825149ce2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5199
the chainentry 5199
- sealed to the entry before
- fda5ca8522fa67af492e2a77708c2337db4845f7c837ecc69aacb1fc994c6ea1
- this leaf
- a0513b437afa63fb7af59b3128889c8f4a4c776da8c487fe8d806255990ccff4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZANtp0SCkkaueS3PEGN55wD3dDOsb26nsz6fKD+lbe5Wwlwc/V0GNFgnV9KetnoSje7Vth0TH5WP3cvU6WlvAw==