For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 55f0c5b524cf5743d2045197d103968e23c41539c7a5065721b5cc55845bedeb
Tx prefix hash: fa2b8a7715ced2d3edee576d17ef449bc6e7ef4b5abd83597cbfe4cc272c28eb
Tx public key: 7d715c8570b6335d1d5edb87b3ae800e954a5fcb849d7b90e26ffb8757c0aa27
| Timestamp: 1781011850 | Timestamp [UTC]: 2026-06-09 13:30:50 | Age [y:d:h:m:s]: 00:006:01:22:02 |
| Block: 8592 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 153 | RingCT/type: yes/0 |
| Extra: 017d715c8570b6335d1d5edb87b3ae800e954a5fcb849d7b90e26ffb8757c0aa27020900000004e49593ff00 | ||
1 output(s) for total of 34.612537140744 HMNY
| stealth address | amount | amount idx | tag |
| 00: a87f1c4d42d26fb284f2f39d20d21e3bb7753eb2863cda79f43e5c6f9a509342 | 34.612537140744 | 10618 of 0 | <24> |
Check which outputs belong to given HMNY address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side
Prove to someone that you have sent them HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side
{
"version": 2,
"unlock_time": 8652,
"vin": [ {
"gen": {
"height": 8592
}
}
],
"vout": [ {
"amount": 34612537140744,
"target": {
"tagged_key": {
"key": "a87f1c4d42d26fb284f2f39d20d21e3bb7753eb2863cda79f43e5c6f9a509342",
"view_tag": "24"
}
}
}
],
"extra": [ 1, 125, 113, 92, 133, 112, 182, 51, 93, 29, 94, 219, 135, 179, 174, 128, 14, 149, 74, 95, 203, 132, 157, 123, 144, 226, 111, 251, 135, 87, 192, 170, 39, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}