why1 reason
spend_windowspend_window_exceeded
this would take GDXXPXC3ZXX6HCECD4RRBEGBO2CGADDX4T2RJ2B4F7QXU4TB766AEPOV to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 9ccc546df2a8955c53ca744a51b42dbd707b23da4267f7362a944e7b2f7f94de
- request
- eced63df094b5ea05c3f7fd650019add19213bc2876135b8e1bec16728922159
- transaction
- 804ad4e9b9b9e8b0fddb97c2b9652e666b7eb30d81cb9e6b94d463f9227d95a0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18566
the chainentry 18566
- sealed to the entry before
- 6bc840fc9afe89421407d5e7f51cf6b61b2064fca1b96dc0336dd7be9742a38c
- this leaf
- 61f1636f4abc2e085b07cfad02b3eb75f96cb90719c69c7650d622dd0669c6c3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tq9f2Qg4Fx2H/uT3PjSXSAUnVhtLOWl6mpdptRw/M1RsbcPAR4dt4vKEhxM24DY10nTb5iRs+VC4vLhdKzGDBw==