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: 1dd38b9fbbe8636b627f7eed5a0211abe16ed5af5f437be9106fe90d144e14a5
Tx prefix hash: a5037329292632fd718e683370d3eea442d231b9becddba1821f9a98f7382062
Tx public key: b6cd847ca83b8db84f3a7485bd23b3369733d95e04b39679518b731b9de39020
| Timestamp: 1780865722 | Timestamp [UTC]: 2026-06-07 20:55:22 | Age [y:d:h:m:s]: 00:001:05:54:26 |
| Block: 7662 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 237 | RingCT/type: yes/0 |
| Extra: 01b6cd847ca83b8db84f3a7485bd23b3369733d95e04b39679518b731b9de39020020900000001e49593ff00 | ||
1 output(s) for total of 34.673988588693 HMNY
| stealth address | amount | amount idx | tag |
| 00: 44df36332f9ecdd6db1a4b1fb7a7b3ebb7400f258fd0cfe60289e0fb0757f4ba | 34.673988588693 | 9474 of 0 | <84> |
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": 7722,
"vin": [ {
"gen": {
"height": 7662
}
}
],
"vout": [ {
"amount": 34673988588693,
"target": {
"tagged_key": {
"key": "44df36332f9ecdd6db1a4b1fb7a7b3ebb7400f258fd0cfe60289e0fb0757f4ba",
"view_tag": "84"
}
}
}
],
"extra": [ 1, 182, 205, 132, 124, 168, 59, 141, 184, 79, 58, 116, 133, 189, 35, 179, 54, 151, 51, 217, 94, 4, 179, 150, 121, 81, 139, 115, 27, 157, 227, 144, 32, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}