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: c9ed111584bdb7418357480e5296f2e1976b940f0a4bab19b978150cc5a152dd
Tx prefix hash: 3655068a2b6b32d5913285ab9feadb7435a3e7500c60c80177a85a33386b7d10
Tx public key: 5d26f456fc0a886dcf9b0d19da3958142ef1283f36b7eb9c78d15af10f43d45b
| Timestamp: 1780824916 | Timestamp [UTC]: 2026-06-07 09:35:16 | Age [y:d:h:m:s]: 00:001:17:14:32 |
| Block: 7239 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 661 | RingCT/type: yes/0 |
| Extra: 015d26f456fc0a886dcf9b0d19da3958142ef1283f36b7eb9c78d15af10f43d45b020900000001e49593ff00 | ||
1 output(s) for total of 34.701975171511 HMNY
| stealth address | amount | amount idx | tag |
| 00: e0c7a6797984986162ac1eec80933f2747d30287402a6e2a1af1be3acdf6f256 | 34.701975171511 | 8915 of 0 | <f8> |
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": 7299,
"vin": [ {
"gen": {
"height": 7239
}
}
],
"vout": [ {
"amount": 34701975171511,
"target": {
"tagged_key": {
"key": "e0c7a6797984986162ac1eec80933f2747d30287402a6e2a1af1be3acdf6f256",
"view_tag": "f8"
}
}
}
],
"extra": [ 1, 93, 38, 244, 86, 252, 10, 136, 109, 207, 155, 13, 25, 218, 57, 88, 20, 46, 241, 40, 63, 54, 183, 235, 156, 120, 209, 90, 241, 15, 67, 212, 91, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}