why2 reasons
spend_windowspend_window_exceeded
this would take GDQC5W35ELIZR56VS6FHY6S3ZNGQSWYNX5KOSZWFRFWNGPBSDLPMVMZV to 70 over the last 60000ms, above the 12 window cap, with 0 already spent
mandateamount_exceeds_cap
op 0 pays 70.0000000, cap is 40
what it was decided fromfingerprints
- rule compiled from it
- 8756be3fd2409269094d05f09964be1ce08b782c815d356ef2ba6b25f08796ac
- request
- becd0876f12ae714cecb0150dba8341ceaf7ea38d1277385e47d71f4c8fc6706
- transaction
- f940cca6e2775f987d3cf1fd956aba22c75b87d941a89288af1f27c3a4d516e9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6102
the chainentry 6102
- sealed to the entry before
- a6290c7e7448a342619ad82a6ff26d14d1d27494d6c66919db107bffd298412a
- this leaf
- 3d8baa0a13de6e78a1fb983e9d5222379f498567138b9094cc775b19bb6aa3df
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a9w/brTPs6DS0jqvySpdkSqLpBZGmJwQY0v8AWtn7IpMeM3AlteYhVGFJAJpokpMd/i6uIL92ZIVJ/bNRoamBg==