why1 reason
spend_windowspend_window_exceeded
this would take GDCRAQ6G54IHZOMUFD4DKLWO7RWZFMGRS6DPJYXEODPFFR5C5KUHJB54 to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- a7cbd9faa35f45c3c0b46281cd9435863f73165c3ae71072e7e27040b907581c
- request
- fb3c690d539e6843238e25d62b9382da665a85ef18afb3a0e708c461ffeec4e3
- transaction
- 48c180d98f1ee3e6fc2a331d5264596cb676b3be0c50512d8447a839ea328d26computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45243
the chainentry 45243
- sealed to the entry before
- b9d5a2a9bc2f7d5544f430650d85db07b215a24c6342655fd4f3e0cde1cf1112
- this leaf
- 99f9b12b74b4759d444165ccd3ef2bec289af5acc79f6a8e8337aa7fd6bdf8fd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DDeqiGbrPYB3RD0QbfBeH+u3PR7NcCU9K47577JizOFUZImoqCSZrJI5qjKnypYuFXG4+1BhRhQt4gFP50KNAg==