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: db4678b9e36a9c13b96ea24b2b7f530dc4e9b04df067c78ad5004f245e4e134c
Tx prefix hash: fcb03fbcac256726014f4a6e562fe3a682b937c2dd937d18b9fc80817fc0b08f
Tx public key: b8d9c7e2b43825be56a5a262065bed6809ead0a00edffffa7fd33691af99134b
| Timestamp: 1781000978 | Timestamp [UTC]: 2026-06-09 10:29:38 | Age [y:d:h:m:s]: 00:004:00:32:38 |
| Block: 8449 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 296 | RingCT/type: yes/0 |
| Extra: 01b8d9c7e2b43825be56a5a262065bed6809ead0a00edffffa7fd33691af99134b020900000001e49593ff00 | ||
1 output(s) for total of 34.638218636414 HMNY
| stealth address | amount | amount idx | tag |
| 00: c111d0f1e8d1379a02459db6327a0bf1c39dbdba23c4337b43032a99257d2cba | 34.638218636414 | 10439 of 0 | <92> |
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": 8509,
"vin": [ {
"gen": {
"height": 8449
}
}
],
"vout": [ {
"amount": 34638218636414,
"target": {
"tagged_key": {
"key": "c111d0f1e8d1379a02459db6327a0bf1c39dbdba23c4337b43032a99257d2cba",
"view_tag": "92"
}
}
}
],
"extra": [ 1, 184, 217, 199, 226, 180, 56, 37, 190, 86, 165, 162, 98, 6, 91, 237, 104, 9, 234, 208, 160, 14, 223, 255, 250, 127, 211, 54, 145, 175, 153, 19, 75, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}