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: ccb2b47037c9f184614bc261255f9b1fef2fe611044bdaf0def4716a6cfe66a5
Tx prefix hash: df68302da4342b1687dd070eb4e26d7a1803c656f7c9bf080d87fd2ce17c781d
Tx public key: fbce986c48538fb03886ed03ce5b882e9b2a7b8eb8d9e21bed4ad16dbc6e4531
| Timestamp: 1779479619 | Timestamp [UTC]: 2026-05-22 19:53:39 | Age [y:d:h:m:s]: 00:017:05:42:18 |
| Block: 637 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7249 | RingCT/type: yes/0 |
| Extra: 01fbce986c48538fb03886ed03ce5b882e9b2a7b8eb8d9e21bed4ad16dbc6e453102090000000493369e7d00 | ||
1 output(s) for total of 35.145023888066 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2c4abc5a1541e8016fabc083f84f70e92a5270387e71ee32fd503d24e259fa84 | 35.145023888066 | 674 of 0 | <7f> |
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": 697,
"vin": [ {
"gen": {
"height": 637
}
}
],
"vout": [ {
"amount": 35145023888066,
"target": {
"tagged_key": {
"key": "2c4abc5a1541e8016fabc083f84f70e92a5270387e71ee32fd503d24e259fa84",
"view_tag": "7f"
}
}
}
],
"extra": [ 1, 251, 206, 152, 108, 72, 83, 143, 176, 56, 134, 237, 3, 206, 91, 136, 46, 155, 42, 123, 142, 184, 217, 226, 27, 237, 74, 209, 109, 188, 110, 69, 49, 2, 9, 0, 0, 0, 4, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}