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: 41e466dc4fbda142f61c05f0c3685ff4104ec2c54907767b34cabb098d4e26ef
Tx prefix hash: 398b759de6e583445ba0e2cf3fb101a5ba3ddd353f0f1b92ae4612b90b43e269
Tx public key: a2b173a32eec29398ebc3c4875c96bc7d5caf993ee0f1f0277f46f3334f281b8
| Timestamp: 1780903540 | Timestamp [UTC]: 2026-06-08 07:25:40 | Age [y:d:h:m:s]: 00:000:15:53:13 |
| Block: 7841 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 45 | RingCT/type: yes/0 |
| Extra: 01a2b173a32eec29398ebc3c4875c96bc7d5caf993ee0f1f0277f46f3334f281b80209000000024a728a4c00 | ||
1 output(s) for total of 34.662152364188 HMNY
| stealth address | amount | amount idx | tag |
| 00: da94b9dda21b75055a6d9a5ad61e93cf23ecf4f683c9999a3fb2424e540ff7ff | 34.662152364188 | 9721 of 0 | <d0> |
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": 7901,
"vin": [ {
"gen": {
"height": 7841
}
}
],
"vout": [ {
"amount": 34662152364188,
"target": {
"tagged_key": {
"key": "da94b9dda21b75055a6d9a5ad61e93cf23ecf4f683c9999a3fb2424e540ff7ff",
"view_tag": "d0"
}
}
}
],
"extra": [ 1, 162, 177, 115, 163, 46, 236, 41, 57, 142, 188, 60, 72, 117, 201, 107, 199, 213, 202, 249, 147, 238, 15, 31, 2, 119, 244, 111, 51, 52, 242, 129, 184, 2, 9, 0, 0, 0, 2, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}