why2 reasons
spend_windowspend_window_exceeded
this would take GB3A4B4AGCK6LH7W2WML7NJRO7I23WVFAXK5OM3QPIUNIDKY7OSV4UCF to 70 over the last 60000ms, above the 12 window cap, with 0 already spent
mandateamount_exceeds_cap
op 0 pays 70.0000000, cap is 40
what it was decided fromfingerprints
- rule compiled from it
- a8fcae2a05f6b781ce61c7c2d6fc76cfe4b9d9cde44819f2b6ca4ca14e6be760
- request
- f70ef663e3c9ab21788250f4b181c36df7aa52a0c9e5d84bf91e154c40070ec5
- transaction
- db08d8da34aded7cad70a7961dcc0f74aca1ccbcda14c4ea0a62ff2f4b6e781fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27872
the chainentry 27872
- sealed to the entry before
- 6746d64b1301ef612ad7cffddf963230541548c8fbd489f17f047f64e01be925
- this leaf
- 1a86c168d366ded8af1c34560741f9c90ba589b318bf458694048ec65536029c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Yhwn4mX+7rdH2d+MJkg4uQ3CI+1mrepkmXtDQtimXdXBdJ3CNFvITmjkfNCWYVCjyNBLEoj1eCY0CrTWSxYnDw==