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: faf5d1517dd48ed42b8fddcfe9a79a02bb9a378c68b97faba66561a9ae436ef6
Tx prefix hash: bcdc057b03efced8e0c81b67793d9add68b48d2db42f6c85252a0eeb7cd0b428
Tx public key: 5685ff810d57ff9818bb058d06ff14b4475a894d2955bacf9e782e42f7a08a80
| Timestamp: 1780891604 | Timestamp [UTC]: 2026-06-08 04:06:44 | Age [y:d:h:m:s]: 00:000:17:05:23 |
| Block: 7730 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 156 | RingCT/type: yes/0 |
| Extra: 015685ff810d57ff9818bb058d06ff14b4475a894d2955bacf9e782e42f7a08a800209000000014a728a4c00 | ||
1 output(s) for total of 34.669491669873 HMNY
| stealth address | amount | amount idx | tag |
| 00: cd14bccdd8c3d9c8af80c0e842a3b8a9c27a9b635535d3fbd15b081e33909c3e | 34.669491669873 | 9568 of 0 | <6e> |
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": 7790,
"vin": [ {
"gen": {
"height": 7730
}
}
],
"vout": [ {
"amount": 34669491669873,
"target": {
"tagged_key": {
"key": "cd14bccdd8c3d9c8af80c0e842a3b8a9c27a9b635535d3fbd15b081e33909c3e",
"view_tag": "6e"
}
}
}
],
"extra": [ 1, 86, 133, 255, 129, 13, 87, 255, 152, 24, 187, 5, 141, 6, 255, 20, 180, 71, 90, 137, 77, 41, 85, 186, 207, 158, 120, 46, 66, 247, 160, 138, 128, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}