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: 4bed39215a0daf708c5674d3a5ba9f164780dda591c8f330ad6c90c6d071d5ac
Tx prefix hash: a60bf098f6d31b8dcb807d5910d6a72d19f63c742027d5aca9d5992c49b0db9c
Tx public key: cc555a33ed25591d95ed2c588322bf532042ff9bc7419abe54160cacc29c8faf
| Timestamp: 1779645867 | Timestamp [UTC]: 2026-05-24 18:04:27 | Age [y:d:h:m:s]: 00:015:07:31:30 |
| Block: 1451 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6435 | RingCT/type: yes/0 |
| Extra: 01cc555a33ed25591d95ed2c588322bf532042ff9bc7419abe54160cacc29c8faf020900000001ba6d17be00 | ||
1 output(s) for total of 35.087198579638 HMNY
| stealth address | amount | amount idx | tag |
| 00: 75febf191771bfe18d7d6aa96f35dc0b95c5a19397e836ebe766e6dfbf37e3bc | 35.087198579638 | 1605 of 0 | <e1> |
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": 1511,
"vin": [ {
"gen": {
"height": 1451
}
}
],
"vout": [ {
"amount": 35087198579638,
"target": {
"tagged_key": {
"key": "75febf191771bfe18d7d6aa96f35dc0b95c5a19397e836ebe766e6dfbf37e3bc",
"view_tag": "e1"
}
}
}
],
"extra": [ 1, 204, 85, 90, 51, 237, 37, 89, 29, 149, 237, 44, 88, 131, 34, 191, 83, 32, 66, 255, 155, 199, 65, 154, 190, 84, 22, 12, 172, 194, 156, 143, 175, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}