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: fcaae8bbe741807566e5bd4d184413e7a65d20b97f5680e19434b0d6e6905dea
Tx prefix hash: 46d9f9ff0844ed9741f8fe58d979d81c647a3b6937cafb7bc584f8a94d50b777
Tx public key: c8729cf5e2c8fa7c2d58e83ca51588a5c1c204045ac5f02909cb60fbe262568e
| Timestamp: 1780692730 | Timestamp [UTC]: 2026-06-05 20:52:10 | Age [y:d:h:m:s]: 00:003:06:46:40 |
| Block: 5811 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2131 | RingCT/type: yes/0 |
| Extra: 01c8729cf5e2c8fa7c2d58e83ca51588a5c1c204045ac5f02909cb60fbe262568e020900000001e49593ff00 | ||
1 output(s) for total of 34.796621653558 HMNY
| stealth address | amount | amount idx | tag |
| 00: cc98529d88216cba5c59dfa4d8fca8ebec923f50af3c7d181c2800271b3a2109 | 34.796621653558 | 7268 of 0 | <3e> |
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": 5871,
"vin": [ {
"gen": {
"height": 5811
}
}
],
"vout": [ {
"amount": 34796621653558,
"target": {
"tagged_key": {
"key": "cc98529d88216cba5c59dfa4d8fca8ebec923f50af3c7d181c2800271b3a2109",
"view_tag": "3e"
}
}
}
],
"extra": [ 1, 200, 114, 156, 245, 226, 200, 250, 124, 45, 88, 232, 60, 165, 21, 136, 165, 193, 194, 4, 4, 90, 197, 240, 41, 9, 203, 96, 251, 226, 98, 86, 142, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}