why1 reason
spend_windowspend_window_exceeded
this would take GDH3HPRY5B3QG6D554JPT2OKSIIHJUT6P7G3AK5QR43FRNVAWPQ7XHNU to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 55fa34f19089946e19bddc5b9ed419e58692f228aac0cddf182a9e808b97400f
- request
- 3bba3a48eb44b9bcf4268a3baababd10dc3e915bfeba5456cca16f061fa0bf47
- transaction
- 0b3777803e4272393040325eca3eabeb9c9aeca1c775ff4594a81c19db6e431acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52240
the chainentry 52240
- sealed to the entry before
- fa66d513c54b33cc810e48bcdb25ac3de0d6ccdb4c4021bcbe52eb1b07cd2be0
- this leaf
- 8e275647797382bb7230ff97850debfffb446c6331945f8888c0bbbad79f6eb0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OJlexP2FUAskzMXMsITPV/4e7kBPydDy32fRVPtW7OfF9u9n3TUa1BQJ+IdDDkFOC02W0ygB6RuKx/bHaTqlCg==