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: dd731ea089d94af49620277feef238c90b30f10a9660492592cf6e8551299865
Tx prefix hash: 27dda177adb433cec33ee053d6d24b8225752fdb491aaa911282820172c36f39
Tx public key: 78fde4e80b77b94e41dfd03bfb3b1aa04e7a00eec316772d22522c4ec5c7542f
| Timestamp: 1780808696 | Timestamp [UTC]: 2026-06-07 05:04:56 | Age [y:d:h:m:s]: 00:001:23:28:06 |
| Block: 6986 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1044 | RingCT/type: yes/0 |
| Extra: 0178fde4e80b77b94e41dfd03bfb3b1aa04e7a00eec316772d22522c4ec5c7542f020900000001e49593ff00 | ||
1 output(s) for total of 34.718724986068 HMNY
| stealth address | amount | amount idx | tag |
| 00: 864e185d6d56679344fbed679e5d8ef68583e0d8df8be1fa9943f0eb13de39c1 | 34.718724986068 | 8616 of 0 | <4a> |
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": 7046,
"vin": [ {
"gen": {
"height": 6986
}
}
],
"vout": [ {
"amount": 34718724986068,
"target": {
"tagged_key": {
"key": "864e185d6d56679344fbed679e5d8ef68583e0d8df8be1fa9943f0eb13de39c1",
"view_tag": "4a"
}
}
}
],
"extra": [ 1, 120, 253, 228, 232, 11, 119, 185, 78, 65, 223, 208, 59, 251, 59, 26, 160, 78, 122, 0, 238, 195, 22, 119, 45, 34, 82, 44, 78, 197, 199, 84, 47, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}