why1 reason
spend_windowspend_window_exceeded
this would take GB5WLPVC6W3CR73WPPAEOIAC74RIS3BD4I6UVO4KKPFJU2R2P5IYF6PV to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- a0fba3595a1d059ccacfec11ba20876fc3dcbbdac75ad9c8d976d9124b060a17
- request
- bd9dc3e1cddeaeaa954aec04b5c143fc28b6c4186ca1b742ff03143c730ef491
- transaction
- 2b2ff84e26286b30b354efa61bd3f8fa4b2055f9fa062fe5d142cab672ee6fd1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3877
the chainentry 3877
- sealed to the entry before
- 2bd14bc04f97e5c0387c5b6c9142f52ca9a5d73d77a21b262877df37c3df6575
- this leaf
- 2635314f02439979cd17e0ed27914b6de6e4fd9609aeb448090693d570d94f84
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OiP2izUMcbBNhwEWoLNykw9MXgnJAxEHtFj3nz/mUDAvbcDu7DBbY+20VRSWV3ldCWDZ/ZODGhKZRCFAvQdeAg==