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: 30cba6c06c1912778ac9a3b59f28e993a95a7203a4d50a8a5d45a5155fcc10c7
Tx prefix hash: eddbc6ede98a2b27fcbb1aa34c2927d45a468a232fc37dab09a47def726f0e4c
Tx public key: 3546c955fd567484df1d1e0bb729095dac3a95329dbc6a8bc1ca42b7a8cdcec9
| Timestamp: 1781000428 | Timestamp [UTC]: 2026-06-09 10:20:28 | Age [y:d:h:m:s]: 00:007:22:54:38 |
| Block: 8434 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 311 | RingCT/type: yes/0 |
| Extra: 013546c955fd567484df1d1e0bb729095dac3a95329dbc6a8bc1ca42b7a8cdcec9020900000003e49593ff00 | ||
1 output(s) for total of 34.622969594294 HMNY
| stealth address | amount | amount idx | tag |
| 00: e37d03619b818d4120956d29a3dab4f0e9617a906874d07fc559d8453947ddac | 34.622969594294 | 10424 of 0 | <6a> |
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": 8494,
"vin": [ {
"gen": {
"height": 8434
}
}
],
"vout": [ {
"amount": 34622969594294,
"target": {
"tagged_key": {
"key": "e37d03619b818d4120956d29a3dab4f0e9617a906874d07fc559d8453947ddac",
"view_tag": "6a"
}
}
}
],
"extra": [ 1, 53, 70, 201, 85, 253, 86, 116, 132, 223, 29, 30, 11, 183, 41, 9, 93, 172, 58, 149, 50, 157, 188, 106, 139, 193, 202, 66, 183, 168, 205, 206, 201, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}