why2 reasons
spend_windowspend_window_exceeded
this would take GBHPPZM4IDX7WHZV4W7BIVUU55QUIZWDF6UWUJXDOOPXHX2DS3V2ZFCQ 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
- a98b0a0b6d8e768ddc0cb3c7b4b4283e840909d72d50d2cda478ae7503ac9915
- request
- ae01c12abf90bfbbb247467cf68570b2a5e98f975f34a6e04688111f146de524
- transaction
- 06d1b16dca3e250268ea2def06ef0404939f571e4ae437fd36d5daf4720475a2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35220
the chainentry 35220
- sealed to the entry before
- 8d0ac4b0176bd420d22174691698d05d3bba8f4e998c0d6991d31429d3138045
- this leaf
- 081ce5cc643288c21f93f37d3d3ccbb99dc2271c858286527c4c2584c575f487
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0qhgZfj4FrhHWNZej6xqCSlCuWkgbIiVxdjas3+l9a/yxgRIFIbsDg9rRzsoe3cGAee4WyYnOG7IESfa6xCyDA==