why1 reason
spend_windowspend_window_exceeded
this would take GDQOEE4O34AK6Z2G3KKOCJ6WHYZF3ZUPP4YJ6NZGURCAIG25ZVLROX5O to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- da9b744b5d14f17271a5352e9051e8ce4e1966681aebdc6bfde12d1e4530379e
- request
- da84dbf523190e0ae5e0a990ddfff5405b21fbd7cbac42f49ac71ea27dc6ec67
- transaction
- 58f3d4660f3d9125b15f2ec2bf1f125a0c6991286750508b68ef5b44acf82ddccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3781
the chainentry 3781
- sealed to the entry before
- e401ae64019e66c38877c2bc5f09b21665b1e3d1e4486fdf1a1e70f8fa6e574d
- this leaf
- 0ee6f06e43a3e36a20f883249ae5126ed3d3045de61c09c4ef7722733f5fa257
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- d47kh3ZG1+OuBsrG9dhGYnMladqNeyGrTgRSqStGi/VThLMPic+1CoEAo3HLugSIRFnTh4wJ9cT5b54r73GTDA==