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: 49b0b560207cc31b608604371f11b6922eaa8e029a905dd4d9e9ecee512ccf37
Tx prefix hash: b13e89388de3c56e50629740b5b4aa0da3bc25024ef1805eb5dc0136b1e9a50f
Tx public key: 4c338e533be42533e1a4e69f71be808023031916da905cef24a8b1f4270e4f6c
| Timestamp: 1780383486 | Timestamp [UTC]: 2026-06-02 06:58:06 | Age [y:d:h:m:s]: 00:006:19:42:30 |
| Block: 5161 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2737 | RingCT/type: yes/0 |
| Extra: 014c338e533be42533e1a4e69f71be808023031916da905cef24a8b1f4270e4f6c02090000000626697be300 | ||
1 output(s) for total of 34.839788485490 HMNY
| stealth address | amount | amount idx | tag |
| 00: 46f8d771415f78e82983765f735b6a3403e88e7ce384d1491d4c1316b8a64ad7 | 34.839788485490 | 6540 of 0 | <05> |
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": 5221,
"vin": [ {
"gen": {
"height": 5161
}
}
],
"vout": [ {
"amount": 34839788485490,
"target": {
"tagged_key": {
"key": "46f8d771415f78e82983765f735b6a3403e88e7ce384d1491d4c1316b8a64ad7",
"view_tag": "05"
}
}
}
],
"extra": [ 1, 76, 51, 142, 83, 59, 228, 37, 51, 225, 164, 230, 159, 113, 190, 128, 128, 35, 3, 25, 22, 218, 144, 92, 239, 36, 168, 177, 244, 39, 14, 79, 108, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}