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: d9ecc004d01ad0c5e598b462cd487942bcd0524792ec89db0d316504c49fc452
Tx prefix hash: 39b552fcf4186af6b51ed36698169e62d53c469e2c30ef7827c05d2090b26b9c
Tx public key: 205f1f05d759b68a7d0af9aea14a4524f64b187b5f9d906ed53f2dddaea7ecf2
| Timestamp: 1780841160 | Timestamp [UTC]: 2026-06-07 14:06:00 | Age [y:d:h:m:s]: 00:001:09:12:53 |
| Block: 7463 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 423 | RingCT/type: yes/0 |
| Extra: 01205f1f05d759b68a7d0af9aea14a4524f64b187b5f9d906ed53f2dddaea7ecf2020900000002e49593ff00 | ||
1 output(s) for total of 34.687152040825 HMNY
| stealth address | amount | amount idx | tag |
| 00: 61f4cf126e41f4dc94a610d9d9bfce2b7fa379db15d1d6b2ff58d7b6bedf8829 | 34.687152040825 | 9193 of 0 | <1f> |
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": 7523,
"vin": [ {
"gen": {
"height": 7463
}
}
],
"vout": [ {
"amount": 34687152040825,
"target": {
"tagged_key": {
"key": "61f4cf126e41f4dc94a610d9d9bfce2b7fa379db15d1d6b2ff58d7b6bedf8829",
"view_tag": "1f"
}
}
}
],
"extra": [ 1, 32, 95, 31, 5, 215, 89, 182, 138, 125, 10, 249, 174, 161, 74, 69, 36, 246, 75, 24, 123, 95, 157, 144, 110, 213, 63, 45, 221, 174, 167, 236, 242, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}