why2 reasons
mandatedestination_not_allowed
op 0 pays GDBVUA6TBQZJ63QNI5NMRO36BOZ6XYFHLDP2XJDU75QLT43HBTPFKYYQ, which is not in the allowlist
counterpartycounterparty_denied
GDBVUA6TBQZJ63QNI5NMRO36BOZ6XYFHLDP2XJDU75QLT43HBTPFKYYQ 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
- ef75a5a996efbe771213f9ea75bf1fc99b2ba11f207eccee43760f854188e146
- request
- d4d587f169d1a31cbe3b3d5bcfa4baff2fc1af7db2cb33e8a251e86f9a326520
- transaction
- 49da211aa2abade86ad62b9cc0c474fd75b2fa90f1bce0f5c0139990ba3df2ebcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30862
the chainentry 30862
- sealed to the entry before
- ecb714f901815d9154fdb9189886b1df2ef5dc3ac884c7447a6166c16fdd6231
- this leaf
- 6907aecb700a1d44623e17f48f0f84fac8d57a16b710a981900813be5b3eea37
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Am9QyVxW8mNf4ewGlzELvlyFYE+8lWhd/YfIsiZ/gyGMu648tdAGz/5BdYO9mFRztLO7DgaA9fglZ00Utd4oDQ==