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: 6ab82f46e091f5a80206aed045cb6b89497af453bdc07469754222fe92988c5d
Tx prefix hash: eb19ab68c465c35c8571cb63d30dc046d41af54082d08c6bcb8cd136ecfaf667
Tx public key: ca5a2ee36801ea8502e601f725fb33ac38deef5aa405ecf1425b970cec4e71ff
| Timestamp: 1779633387 | Timestamp [UTC]: 2026-05-24 14:36:27 | Age [y:d:h:m:s]: 00:015:06:35:40 |
| Block: 984 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6902 | RingCT/type: yes/0 |
| Extra: 01ca5a2ee36801ea8502e601f725fb33ac38deef5aa405ecf1425b970cec4e71ff020900000001ba6d17be00 | ||
1 output(s) for total of 35.118465816703 HMNY
| stealth address | amount | amount idx | tag |
| 00: d4df64f3770bbf76a8389ab9e069967f8a14362ef7cfb8ebe2d6ef33e43f09b3 | 35.118465816703 | 1120 of 0 | <39> |
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": 1044,
"vin": [ {
"gen": {
"height": 984
}
}
],
"vout": [ {
"amount": 35118465816703,
"target": {
"tagged_key": {
"key": "d4df64f3770bbf76a8389ab9e069967f8a14362ef7cfb8ebe2d6ef33e43f09b3",
"view_tag": "39"
}
}
}
],
"extra": [ 1, 202, 90, 46, 227, 104, 1, 234, 133, 2, 230, 1, 247, 37, 251, 51, 172, 56, 222, 239, 90, 164, 5, 236, 241, 66, 91, 151, 12, 236, 78, 113, 255, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}