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: b1491574339a395f44a6169f24057434d29906c88f2e81bbf4826bf5797e10fc
Tx prefix hash: 73a2972ecf5169c03f6e8c9d4a7573e99ff675d7d1d80f937cbdfea53d5b08ae
Tx public key: b2222aba05eef803c8425107763190b1342d47c4b95a5075aab2f151f324b534
| Timestamp: 1780831342 | Timestamp [UTC]: 2026-06-07 11:22:22 | Age [y:d:h:m:s]: 00:001:16:28:36 |
| Block: 7345 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 621 | RingCT/type: yes/0 |
| Extra: 01b2222aba05eef803c8425107763190b1342d47c4b95a5075aab2f151f324b534020900000002e49593ff00 | ||
1 output(s) for total of 34.694959864939 HMNY
| stealth address | amount | amount idx | tag |
| 00: ae09aa45ec28ba8a99fdc1e048eed68f28abb7f0f52432feb83008b8001c9ca7 | 34.694959864939 | 9043 of 0 | <0b> |
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": 7405,
"vin": [ {
"gen": {
"height": 7345
}
}
],
"vout": [ {
"amount": 34694959864939,
"target": {
"tagged_key": {
"key": "ae09aa45ec28ba8a99fdc1e048eed68f28abb7f0f52432feb83008b8001c9ca7",
"view_tag": "0b"
}
}
}
],
"extra": [ 1, 178, 34, 42, 186, 5, 238, 248, 3, 200, 66, 81, 7, 118, 49, 144, 177, 52, 45, 71, 196, 185, 90, 80, 117, 170, 178, 241, 81, 243, 36, 181, 52, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}