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: 8ca21c71a1154cbd7137388f3e9460a67cd31762207c4978852a3a031382a07c
Tx prefix hash: b20b41b96d0f27dfa0e7f012fee258dfe22f973288df3fdfb2ef5fa583b2548a
Tx public key: 9e465184cdb3ca44039e750908c75efc15c46fea6ec097bc902ab2f6b08e66cc
| Timestamp: 1780902985 | Timestamp [UTC]: 2026-06-08 07:16:25 | Age [y:d:h:m:s]: 00:000:16:02:28 |
| Block: 7837 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 49 | RingCT/type: yes/0 |
| Extra: 019e465184cdb3ca44039e750908c75efc15c46fea6ec097bc902ab2f6b08e66cc0209000000034a728a4c00 | ||
1 output(s) for total of 34.662416816685 HMNY
| stealth address | amount | amount idx | tag |
| 00: 38a04852885f0ccf470772b48e697d1017699f9d24abcd382c6884df315755fe | 34.662416816685 | 9715 of 0 | <06> |
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": 7897,
"vin": [ {
"gen": {
"height": 7837
}
}
],
"vout": [ {
"amount": 34662416816685,
"target": {
"tagged_key": {
"key": "38a04852885f0ccf470772b48e697d1017699f9d24abcd382c6884df315755fe",
"view_tag": "06"
}
}
}
],
"extra": [ 1, 158, 70, 81, 132, 205, 179, 202, 68, 3, 158, 117, 9, 8, 199, 94, 252, 21, 196, 111, 234, 110, 192, 151, 188, 144, 42, 178, 246, 176, 142, 102, 204, 2, 9, 0, 0, 0, 3, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}