why1 reason
spend_windowspend_window_exceeded
this would take GD6K43OW7RMQQFTSGYYIXGKNHP7O4FQCYVRCS7ULC3G6EQUC7RCMKZ7B to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 89083b6d2036a850ce4f44f7d5316b4e902f5872e6c121e9f9fb80ce83ad021f
- request
- bf75b9e3e4bcdefd9f0d54d77cc46849ba106df6b18323c99d046ab108f896a4
- transaction
- 646bb38177565908d54bfb872f9a998fb1e0ebad22dbdbf996296e7c6b74b2b8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55413
the chainentry 55413
- sealed to the entry before
- 402312eeac614c9b019de84a6a6d2dce3ef78f57d004080de518c9bb5ba0e01a
- this leaf
- 31384cadd107285aca6973d4850169c2f3eaa8db61e76a777f71d99fcbec89a7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4Tdt9Ro4PLK3a4m9dPYPgAUBtSPav6fjCqZ/uJO1U8+M701CHf6j0hodaMzUspludo5JaGh7ixtEXcSqF5e9Bw==