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: 0498515ad6681dded696e52481c323d3c0c3a793687706f103c9975a53fdc9e5
Tx prefix hash: 0ceb1802f39cb8f1d805b5f8e8510d52b7a36a0a5bd95920a13ba9830d1cb108
Tx public key: 1ccf5222f3a6d20a5566ff9714bc7dce0e2ca312d9bdfc2289f50258b6597854
| Timestamp: 1780688880 | Timestamp [UTC]: 2026-06-05 19:48:00 | Age [y:d:h:m:s]: 00:003:03:30:53 |
| Block: 5552 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2334 | RingCT/type: yes/0 |
| Extra: 011ccf5222f3a6d20a5566ff9714bc7dce0e2ca312d9bdfc2289f50258b6597854020900000001e49593ff00 | ||
1 output(s) for total of 34.813815562313 HMNY
| stealth address | amount | amount idx | tag |
| 00: fed134c3924fcba4b3c765d941def07a3e7b0f7e1fa4e71b8837e8fbce49dba4 | 34.813815562313 | 6995 of 0 | <4c> |
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": 5612,
"vin": [ {
"gen": {
"height": 5552
}
}
],
"vout": [ {
"amount": 34813815562313,
"target": {
"tagged_key": {
"key": "fed134c3924fcba4b3c765d941def07a3e7b0f7e1fa4e71b8837e8fbce49dba4",
"view_tag": "4c"
}
}
}
],
"extra": [ 1, 28, 207, 82, 34, 243, 166, 210, 10, 85, 102, 255, 151, 20, 188, 125, 206, 14, 44, 163, 18, 217, 189, 252, 34, 137, 245, 2, 88, 182, 89, 120, 84, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}