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: ed624f7b8a017825f2b7ef537fc0a1e0de6d940de55236b6cd7c24929eedf3fa
Tx prefix hash: 9ee13bab8410aa148efb9384709df01b92f15bce1220529a120fca4c81140bae
Tx public key: ea5c954cc204b3f7423ca7b33e4003bbfedd0799307488cbc2d9e9a38daa509b
| Timestamp: 1780804659 | Timestamp [UTC]: 2026-06-07 03:57:39 | Age [y:d:h:m:s]: 00:006:07:04:37 |
| Block: 6916 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1829 | RingCT/type: yes/0 |
| Extra: 01ea5c954cc204b3f7423ca7b33e4003bbfedd0799307488cbc2d9e9a38daa509b020900000001e49593ff00 | ||
1 output(s) for total of 34.723360749837 HMNY
| stealth address | amount | amount idx | tag |
| 00: 136bf69f6295574bf03056cf3aa18f7ef165c5a8df8187b7ed710c327fd531be | 34.723360749837 | 8532 of 0 | <29> |
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": 6976,
"vin": [ {
"gen": {
"height": 6916
}
}
],
"vout": [ {
"amount": 34723360749837,
"target": {
"tagged_key": {
"key": "136bf69f6295574bf03056cf3aa18f7ef165c5a8df8187b7ed710c327fd531be",
"view_tag": "29"
}
}
}
],
"extra": [ 1, 234, 92, 149, 76, 194, 4, 179, 247, 66, 60, 167, 179, 62, 64, 3, 187, 254, 221, 7, 153, 48, 116, 136, 203, 194, 217, 233, 163, 141, 170, 80, 155, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}