why1 reason
spend_windowspend_window_exceeded
this would take GDQU6E5KYXVCTZJCFRI7QFYOMHBQ3B45IJS6MZNN63T345IG4ZCUI5K7 to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 902f098040de9a2f19191d9d18e9bb847340bb343fbdcaddb19ebf90cb3b8666
- request
- 20863ebdb023aa8e69e642edd668b3491e78534fe90a3be7b09b439a2dbfadb7
- transaction
- 3216d24fc524c8af5dc6d2310e21fafc2cc1e000cfdd26045e62476a0e94a16dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51645
the chainentry 51645
- sealed to the entry before
- 916a6fb26f3819eba7f822c8e10fc6b4831fb5f7212ab36ac3eebeae80972d95
- this leaf
- c2d16c26ca81da86750543902f102eee4b4efcd38d8d5ba019c77f3b9ef9e2f3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VqvycSETOr4d7iP1vZbuhnXjrvp0zXz95rsnvPymcuYbM67pxnVaSiBgP9fWG3bwbzcm3oPz3cSwABhwBZQJBg==