why2 reasons
spend_windowspend_window_exceeded
this would take GD53GS3BA6LIIA52H6BXG6LG33L4FH4YQ7MYB6ZUHCP4KPUCHXOPN2W4 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
- 05fb14868067e60b9510da6eff2d13a40d901a10bb4e7ccdf6ea67943954b61e
- request
- bce2fbb56e72bcba4d92c80815657f5c3c1f163a2a4687f9d33c87e1f0e0132d
- transaction
- 3b190f63c2d75aeefd2460d63498fd407494d8c8786760a911ab1c232ce87d85computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60546
the chainentry 60546
- sealed to the entry before
- 24874c38a01f2bf6474f41466b5914ef4e31630c083a10853dc3e9c0b51734f5
- this leaf
- f3bb6aea2036e2a6690d73f10eb55021bcdc9cdb7739420004faf4c5998a82d2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gZWqgM/CfH8t0J/h89W9eSDHIMwWSnNFsSV7pUNTIBqYb9Jn1unitQ+WptLqScbVBIVDL/iYg1UWPQmQMCQVCQ==