why1 reason
spend_windowspend_window_exceeded
this would take GBKV4B2KC42B6PUDJFSVRSNKVRSXMBWOWUPCQFHUV4R4CUA5G55FCAYD to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 4f372a9e3c636e9b1ac75ade755b1ea477c12ce55f9b032052fd13ebffe8b999
- request
- f0a7ec228d94c233596728fdd5a9f11bdacdf15ac9aecff3aa298e62b8acca90
- transaction
- 3f19f022e2fa0145457cd95b319387800165a6699948bd57020d76f37a38ab66computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51370
the chainentry 51370
- sealed to the entry before
- 662c947d57951633ca07d1c919d2a58f85d78ec981f92a4843fd1e0019ce6aa6
- this leaf
- 021f9d429d3e6c1d6dbb5043e27e49317ebeda8f6e29fffed7d0d3df71462a4e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vSwbMBUI43XWYOP7zbXa6KeEkzehV5RKZ4THL8gPjjLAcdeUK921H7LK8wVXZih2m8mL1GXRWWsb9HhYgEbCDw==