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: a4697d474c7482283898a2b13f8e9583b671f9961b7e94f0abd135f84df7592f
Tx prefix hash: 58cbfaff5355a01d8afe87b8fe44f2b6bcc5226f8e6408d3fb1dd4a5d4fb1bee
Tx public key: 47cffba06e8a7d7758bc15a5ac25620d1f34b5ffacb107ba9ffc63b1d504302a
| Timestamp: 1779707104 | Timestamp [UTC]: 2026-05-25 11:05:04 | Age [y:d:h:m:s]: 00:022:21:31:10 |
| Block: 1564 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7181 | RingCT/type: yes/0 |
| Extra: 0147cffba06e8a7d7758bc15a5ac25620d1f34b5ffacb107ba9ffc63b1d504302a020900000004ba6d17be00 | ||
1 output(s) for total of 35.079637029541 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9043443f3c5995fc189beb6a012414f90eef626d6a6e6b4fe68e95aea8bc659e | 35.079637029541 | 1722 of 0 | <7a> |
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": 1624,
"vin": [ {
"gen": {
"height": 1564
}
}
],
"vout": [ {
"amount": 35079637029541,
"target": {
"tagged_key": {
"key": "9043443f3c5995fc189beb6a012414f90eef626d6a6e6b4fe68e95aea8bc659e",
"view_tag": "7a"
}
}
}
],
"extra": [ 1, 71, 207, 251, 160, 110, 138, 125, 119, 88, 188, 21, 165, 172, 37, 98, 13, 31, 52, 181, 255, 172, 177, 7, 186, 159, 252, 99, 177, 213, 4, 48, 42, 2, 9, 0, 0, 0, 4, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}