why3 reasons
spend_windowspend_window_exceeded
this would take GDXLXJXF24QLFTUXGRJJNUBANNJAZ7TTKON4JORNEO74VNZEHUROAZRS to 999700 over the last 3600000ms, above the 2000 window cap, with 0 already spent
mandatedestination_not_allowed
op 0 pays GBL67IWTY3WX22ARTALQPWN74QWB2BFPZBQ4RCEIMT5GHYPGCODYQELW, which is not in the allowlist
mandateamount_exceeds_cap
op 0 pays 999700.0000000, cap is 500
what it was decided fromfingerprints
- rule compiled from it
- 0b4c0e95c842edc972417c5e8118b30e5000f5015ddb80f5f308bd356c4a5c66
- request
- a1e12d9b310742718fbb57c31798e70239a7f394f0c44abad938a1252f5e0b88
- transaction
- a0d74bb0bfada6914757e74f89ad47fa7fa3ba69853cf43980ae004a7825ae03computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50777
the chainentry 50777
- sealed to the entry before
- 8d923c5832aed97e99f00528e62731e47a695bc90ddabee1b24a1afd13d2a210
- this leaf
- 7ad2b1ea31de653a40ad7042726461aa1532bccf6197ec3dda8cf89b3ca20a29
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Yum+I4BwdCwaeZrIcWwwPvDrL3EZFJZl9kDxMoYnbxYuRupr7240KEkcrQD9NsU14+7bWYHreqseFdjlFsIpBw==