why1 reason
spend_windowspend_window_exceeded
this would take GB33QRS23PI43U567NNIPLOXE24RCGRSCJAJF55WD6RKYTUYRE7SHCMM to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- e4830b0bbd34d2f1e557bddcaeebbaecffd1f2c4f5c7feafc5995755b5db6108
- request
- 31ab7ebe745b1304a72b4b1915443403b8dc31c116c1790ec3e1cd0a5814d6b7
- transaction
- 4a3238efa03cd731a815a543d075e9511c7339a93fed4e12d371ea53ded0e48ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42103
the chainentry 42103
- sealed to the entry before
- 47351fa9ca7d2b0da932fb168a7917e94c88a82c9e994bb3e4d814a651865b05
- this leaf
- f7617e79d4a85e264fb4ce2c9cd4c6965e416cb87cbbebaa5493483dc6d4273c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CR7oC3ZWGPQAdMGPc4tREdzJunseAkr/dsFpEpVTiAXFAa8AR8ACcgrwrHGamwFi+Zcr4eFQIPTYnx0qcd9FCA==