why1 reason
spend_windowspend_window_exceeded
this would take GDWHXOGJ3F44F3IZK3JZ7CKEMFPAPUDKNSDHQCNODSAZEQPT225XSR4P to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- f6af4011e71e933b25c8650be6a4bbb0543d847384e2e091fd4a7360e944ab41
- request
- 6a0d3b3f001d8167daa556dcba2db8af884966db5360652359643a3e26870d96
- transaction
- a2838cab4bbf6f85fc879b2dac812322c378954a0bf2a40fee315a71c51ca5c3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10129
the chainentry 10129
- sealed to the entry before
- 8f5d2659f7bd1ab727e244dd55d67ffca9930f06ef572555ffa3659f38fa1006
- this leaf
- 3adbe595c3c97fcfc391ec6ec2a0b558035a60f78fbe4b77d7ae6b9bcacc1ab2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- n0TY/Zxv7pAuFayr9oodD9E7Pwqt2i0VfuA5MKwYL7Yje5nv2xkZXqOplh55wAFY62ZTHmceQ1BpHu4ehKOCCQ==