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: 5f05b3a29650a716930a4f7be89a39ea22e29e72024de1f7eb929e45e2f4bdbf
Tx prefix hash: 76b123ca1512ce4c0f0cb05e515fe762a8c9006c4e0d1ae60b293fbe5f7247f9
Tx public key: ccc763707c586f28ad84ec3db3991075a27d202b32abe8fd46af668bded11718
| Timestamp: 1780322725 | Timestamp [UTC]: 2026-06-01 14:05:25 | Age [y:d:h:m:s]: 00:007:12:35:11 |
| Block: 5012 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2884 | RingCT/type: yes/0 |
| Extra: 01ccc763707c586f28ad84ec3db3991075a27d202b32abe8fd46af668bded1171802090000002c26697be300 | ||
1 output(s) for total of 34.849691193834 HMNY
| stealth address | amount | amount idx | tag |
| 00: 33761245f12d9d42ef0d2412a5de95a6b5ecf87cbe30bd5b8c102a9ba0595574 | 34.849691193834 | 6385 of 0 | <8c> |
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": 5072,
"vin": [ {
"gen": {
"height": 5012
}
}
],
"vout": [ {
"amount": 34849691193834,
"target": {
"tagged_key": {
"key": "33761245f12d9d42ef0d2412a5de95a6b5ecf87cbe30bd5b8c102a9ba0595574",
"view_tag": "8c"
}
}
}
],
"extra": [ 1, 204, 199, 99, 112, 124, 88, 111, 40, 173, 132, 236, 61, 179, 153, 16, 117, 162, 125, 32, 43, 50, 171, 232, 253, 70, 175, 102, 139, 222, 209, 23, 24, 2, 9, 0, 0, 0, 44, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}