why1 reason
spend_windowspend_window_exceeded
this would take GDTO6WXM6WL2UGEFH5ZC2PPY3FUAO5454UX6C67SCXBRX3HP7BUIPPLE to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- ff6c8776eff6a42bc666843ef39282066d5a783e86c9f43133d35275c0f6084c
- request
- f9cec4a1409c604d9931c869f7a58885927fc5994bf0c25bab83a472c2c5b0ea
- transaction
- 4a63d90d5d5b0c82012e159f704581a6c30ca05010359627b24c1c964ffab147computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37672
the chainentry 37672
- sealed to the entry before
- 142aa50afa51830c2e2d0e90bf9ea187d6565cebffd0d49ee7781f35ffdbba30
- this leaf
- 10da5316271a90b77b97f3642e963726b53e835918de0d9bce9bf6e27baa2ee7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- n2MJTEu/FH7NEeyBhFj/JsvBvD5nX4nN/bHo0OaqERi6fJcWBei1BZtMUm9N09NdJ1rtvApKVJXzGMSjx2zHBg==