why1 reason
spend_windowspend_window_exceeded
this would take GD5OLQU23W7H4NDDD4OOOATNQ7DMVXBBH3KYKCMSIWSTJW3UDNHG2H7I to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- a250417471af168a61c2fae83ecf8ff13b4014283808c80758bce6e55f004de4
- request
- 703aa27f55f29a0ac884fa47f072ace37976eadc559b8d2c238ac9a5dbc7e670
- transaction
- 2d7ec3604596f3f8579879b2ba0a91454bdf37ab4444be18655f6f2d93804ec5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39640
the chainentry 39640
- sealed to the entry before
- 29729ba7bbae4279083b74f2b511e37a98e1461936609c0de0e13a9779dcde52
- this leaf
- 05ce007006f674bb8d8249ee6c9803dfaf01e4f971c4bbd9767cb4caec259c6d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dKQ09ePF1pnnIPer8gnKevkCOU8/unXdnLnUSuzODrScbx6uCkIZHWyNFBuFeyQU5MNjZYFwqKQ4HJWdDVq8CQ==