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: d1a5290ed75a5628b8edbe6069e1d6b4a850ee2edcd749fcc74976feebaea019
Tx prefix hash: cd5ccce963f7a71d8f2b59410a2ef0c468eecd1cb2fba898202336286eacfe84
Tx public key: c7b2abe0c082725a0869458d26be6f9d176ce604bedf3e562d917c8f1c8cb3d4
| Timestamp: 1780077279 | Timestamp [UTC]: 2026-05-29 17:54:39 | Age [y:d:h:m:s]: 00:010:07:41:18 |
| Block: 4716 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3170 | RingCT/type: yes/0 |
| Extra: 01c7b2abe0c082725a0869458d26be6f9d176ce604bedf3e562d917c8f1c8cb3d402090000000326697be300 | ||
1 output(s) for total of 34.869372038952 HMNY
| stealth address | amount | amount idx | tag |
| 00: 591847ac929e8ff295b2e1a475e002b867aae6b202aa561684f4fe0c555f60be | 34.869372038952 | 5926 of 0 | <64> |
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": 4776,
"vin": [ {
"gen": {
"height": 4716
}
}
],
"vout": [ {
"amount": 34869372038952,
"target": {
"tagged_key": {
"key": "591847ac929e8ff295b2e1a475e002b867aae6b202aa561684f4fe0c555f60be",
"view_tag": "64"
}
}
}
],
"extra": [ 1, 199, 178, 171, 224, 192, 130, 114, 90, 8, 105, 69, 141, 38, 190, 111, 157, 23, 108, 230, 4, 190, 223, 62, 86, 45, 145, 124, 143, 28, 140, 179, 212, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}