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: 7cb932006a1d3fd7343c3091bee0e444745f0bacafe7dfbb14447f936a2e1c4b
Tx prefix hash: c94f04b3725f138ef414a4a45f8d3ed19ed7952e26675c381ead70eb101da817
Tx public key: d42746b3582a0f4b8c00c0dc9f5e6a4be05888f01dee9fe2b16e48734dd9c966
| Timestamp: 1779952443 | Timestamp [UTC]: 2026-05-28 07:14:03 | Age [y:d:h:m:s]: 00:011:17:32:44 |
| Block: 3640 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4246 | RingCT/type: yes/0 |
| Extra: 01d42746b3582a0f4b8c00c0dc9f5e6a4be05888f01dee9fe2b16e48734dd9c96602090000000626697be300 | ||
1 output(s) for total of 34.941008252697 HMNY
| stealth address | amount | amount idx | tag |
| 00: 19e5f98d062fb67ea1e7758c75c24d75a148f66e518667d7294350a5ccef44bd | 34.941008252697 | 4398 of 0 | <a0> |
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": 3700,
"vin": [ {
"gen": {
"height": 3640
}
}
],
"vout": [ {
"amount": 34941008252697,
"target": {
"tagged_key": {
"key": "19e5f98d062fb67ea1e7758c75c24d75a148f66e518667d7294350a5ccef44bd",
"view_tag": "a0"
}
}
}
],
"extra": [ 1, 212, 39, 70, 179, 88, 42, 15, 75, 140, 0, 192, 220, 159, 94, 106, 75, 224, 88, 136, 240, 29, 238, 159, 226, 177, 110, 72, 115, 77, 217, 201, 102, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}