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: 6f36b5a95ae1e6f15cd0c00046684f2af729b2464dbd54f62a09aac471b817a0
Tx prefix hash: a624b5ed4e6b41172243c1c89b21c685c441f7f84ef812f8ad15bd74c93a739c
Tx public key: f0c085bbe2dcea50fc2c98b4bc48ffca36a390ebff42c20b1d1a6f594c0bee40
| Timestamp: 1779731336 | Timestamp [UTC]: 2026-05-25 17:48:56 | Age [y:d:h:m:s]: 00:014:07:47:01 |
| Block: 1886 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6000 | RingCT/type: yes/0 |
| Extra: 01f0c085bbe2dcea50fc2c98b4bc48ffca36a390ebff42c20b1d1a6f594c0bee40020900000001ba6d17be00 | ||
1 output(s) for total of 35.058098894207 HMNY
| stealth address | amount | amount idx | tag |
| 00: d8424947ff6397247cfe5253c5e6d38717d9c3d4c901b8e542d571f6882713d9 | 35.058098894207 | 2103 of 0 | <af> |
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": 1946,
"vin": [ {
"gen": {
"height": 1886
}
}
],
"vout": [ {
"amount": 35058098894207,
"target": {
"tagged_key": {
"key": "d8424947ff6397247cfe5253c5e6d38717d9c3d4c901b8e542d571f6882713d9",
"view_tag": "af"
}
}
}
],
"extra": [ 1, 240, 192, 133, 187, 226, 220, 234, 80, 252, 44, 152, 180, 188, 72, 255, 202, 54, 163, 144, 235, 255, 66, 194, 11, 29, 26, 111, 89, 76, 11, 238, 64, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}