why1 reason
spend_windowspend_window_exceeded
this would take GB5A5DJJKCDE6H6ML2H5BSOC7K34BA7NMGU5JZVTADKCXLX2RJMXP65N to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 1517e780c26e24870223945a6cc3df97cc508c1c4c5139d946b5affaf52d9caf
- request
- cfb1e716f578031de29d5914053611b626831c2ec66e69d581d5c55985289b53
- transaction
- ace7f44dba4041b326ca52b3387ef7aea251931a7db12b6aeaaa348dbf67ebbbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7486
the chainentry 7486
- sealed to the entry before
- c1f935f83475d525c500b4308129bf769d6c9eb67ab924c70aa286548e684d14
- this leaf
- f42063581d9bcfd1fb91a4f2ed7969c72ef566d4fa164c6be134390fdad9e958
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- N15Fa7vi7MphugxHzUF1BMy/12tbDvw1a+KXtfJKoOGdkk8Pw/vhufBOdqlCxoyXvMqH75tbBkL8lVRAWQ47Cg==