why1 reason
spend_windowspend_window_exceeded
this would take GDPQ5KETMKN353UMR4SYSN4DVGLKIBAHTTUUUTF3UOKNZ2YDVJH4GUBI to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 7f78acafeb69a14870990dec2b0d459deda0cf9d91b24bc2d49f858f88aac6f7
- request
- d81f7a68ea50624fb6e9c00c1f77008e1b539b3e43628198c78b922aa4549790
- transaction
- 382346a022d78b88ef326f92a2a6dbf0bd65c9581d70b5424ebf9e1cca15d9f4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11779
the chainentry 11779
- sealed to the entry before
- 73c49e7646c3e8a8f4ec7a7510fd65e6ae58676096718ce78a27824e66684844
- this leaf
- ac86e65c9196351827c8da42fc7c62fd27b31f1bd99259c848267f23ab8f9317
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xdwgzt9fb2SA4fLLc+YRDrvhza7GUc3/9rt1A0LpvYRaVDMDmu/lLeoml0XAU137QbtNvM7sUV6gn3YJa0yUCQ==