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: b3432c860e0f943fd21c00c335651ba0771dec3197f2cf22aa6ed8d944e317f4
Tx prefix hash: 2da0d1388f5fcc272b9bd668b5c7a3de18746988a86b768675db59a75929eb6b
Tx public key: 9672f9cc54efe7927591430f2dfc9c8d6fcabee17487d7d469aafb82983dec2e
| Timestamp: 1780706381 | Timestamp [UTC]: 2026-06-06 00:39:41 | Age [y:d:h:m:s]: 00:003:00:56:16 |
| Block: 6114 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1772 | RingCT/type: yes/0 |
| Extra: 019672f9cc54efe7927591430f2dfc9c8d6fcabee17487d7d469aafb82983dec2e020900000001e49593ff00 | ||
1 output(s) for total of 34.776517549806 HMNY
| stealth address | amount | amount idx | tag |
| 00: b1b1da285a48a829af185cff34c7d79255de46bfd492ad305fc70f0632706fad | 34.776517549806 | 7587 of 0 | <50> |
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": 6174,
"vin": [ {
"gen": {
"height": 6114
}
}
],
"vout": [ {
"amount": 34776517549806,
"target": {
"tagged_key": {
"key": "b1b1da285a48a829af185cff34c7d79255de46bfd492ad305fc70f0632706fad",
"view_tag": "50"
}
}
}
],
"extra": [ 1, 150, 114, 249, 204, 84, 239, 231, 146, 117, 145, 67, 15, 45, 252, 156, 141, 111, 202, 190, 225, 116, 135, 215, 212, 105, 170, 251, 130, 152, 61, 236, 46, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}