why2 reasons
spend_windowspend_window_exceeded
this would take GD3H2EOWKXYIWK6FVXY5WZGPVQNKIMBZVM4XIWPG2XUO6F4FRT2B4IX5 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
- a65b5cc89e18f1c723163f5bffbef687daed075055ce69dcca3a780285333ef5
- request
- 4b2ff1c5913db42c0fd5739cc9155c047842987d63a510fb405dc64a17b1700e
- transaction
- 79394cb236c7de2677245df234c29dfcaf59114821ff4dd7823aad726b425f34computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30733
the chainentry 30733
- sealed to the entry before
- e2e69d8a678d96f3df605fa34a2cef585fd6490ca43f27ee7ee223794c2e79dd
- this leaf
- 08b3f71b6ce9ef2933b355594a006f78dcd7213702ae3d6c2dd5fdb3b6263b6f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JmVj+lJL4u2jQ5GCLZtUDyVyB4CXZp4RRd1zid5JvdwK98ncO2/kcyhXQ6BpXqsBws5qdpwuZACeWTd9IHYnCw==