why1 reason
spend_windowspend_window_exceeded
this would take GC3EHA4H2NO6LN4LLACQC4UKZCISD3PHQIMWZEAUM3PWIPPNRGIWXPZ6 to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 78e437246ee2e093b97cf75bb47535d7ac163b0f58b6d22106ba85764a470bb5
- request
- 78c3a481884ba6ea5d06ee79127ea230dce68486e6d0ace8a792ac58c0b37bb2
- transaction
- b70ddee12f889b131748a1ba6e966fcbe42a72b38254ccfce45f28792ae807cdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48100
the chainentry 48100
- sealed to the entry before
- 470dc843491936b415c3ca610ac2b859c38b0822e45e85f744ddce67219fa4a0
- this leaf
- 04449c384f24477e9d94bac2894c9363b91d112d43c2a8639bde7c381d1d6068
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WrUN91CEcDbiETkslv7ke6QeZzFILYCz2qA3RJI7fY9/T43U9XZY14TSaZJwmvTA1URjLDASTJV/cYd1hwIzCg==