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: 198c2e3c6c5a2a6f95f13b698f3f7ec821cf222417081645158171ceea533316
Tx prefix hash: 195019c32aa776942d95b81ccc8ef899c2de2bafc5c240e4fbec69b999f65597
Tx public key: 01bc80678b3887ef03c8babbb7bb1bd5f56b8a36a3a0fff4ef5f17a58adc042f
| Timestamp: 1780686337 | Timestamp [UTC]: 2026-06-05 19:05:37 | Age [y:d:h:m:s]: 00:003:04:13:16 |
| Block: 5424 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2462 | RingCT/type: yes/0 |
| Extra: 0101bc80678b3887ef03c8babbb7bb1bd5f56b8a36a3a0fff4ef5f17a58adc042f020900000002e49593ff00 | ||
1 output(s) for total of 34.822316074728 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9f64c41a96dbca8862f257742279e4d8083f7101db044c39c34577745183167c | 34.822316074728 | 6861 of 0 | <c5> |
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": 5484,
"vin": [ {
"gen": {
"height": 5424
}
}
],
"vout": [ {
"amount": 34822316074728,
"target": {
"tagged_key": {
"key": "9f64c41a96dbca8862f257742279e4d8083f7101db044c39c34577745183167c",
"view_tag": "c5"
}
}
}
],
"extra": [ 1, 1, 188, 128, 103, 139, 56, 135, 239, 3, 200, 186, 187, 183, 187, 27, 213, 245, 107, 138, 54, 163, 160, 255, 244, 239, 95, 23, 165, 138, 220, 4, 47, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}