why1 reason
spend_windowspend_window_exceeded
this would take GCPJYU5AJFDXAUMFBVKTRZEQHSDIFYVNMTNVHPL426437RQLVTMIGTMX to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 668aa9d12790a5ee55ffdafea15635e8fe095ac332292323457810cd419057e3
- request
- e4ba5b3a82c4b3542aa9c736b8a6b594358044aee54fb9ded56b16bfd1c9cee7
- transaction
- c47df6a5fb45cb76a1ac5e79c66d96571ef4b22859eae97cf22522145e51f264computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48444
the chainentry 48444
- sealed to the entry before
- 2cff64ae92364ab410cce8ec85be5d297d5aff277316678991e158d2eb9ca78a
- this leaf
- 54ef14f1f7b0d45e88964850fa2207c9f33022da16cb26a32774ed74d40d17db
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VzqJPXQWxs/H9EZ8HiIHqaPkztQgG10MrjLTcfb0UwgYCIlSmAkmxAg3E/Fqw0wJZ1PTfqkotDEOnpvmz5FnBg==