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: e912841789af994bfbb97e8a74d3eff1f42044d736bc6148e202592eae58fc36
Tx prefix hash: f2f620ac9e0d9d3185ee98dad91e6e9bcb2013532bf70dba49bde9be58a877bc
Tx public key: b9cd99eb5dd649dc7e07f9761247b962b260e11a3883e1bd580efb017dfa2d54
| Timestamp: 1779469604 | Timestamp [UTC]: 2026-05-22 17:06:44 | Age [y:d:h:m:s]: 00:017:10:32:06 |
| Block: 548 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7394 | RingCT/type: yes/0 |
| Extra: 01b9cd99eb5dd649dc7e07f9761247b962b260e11a3883e1bd580efb017dfa2d5402090000000893369e7d00 | ||
1 output(s) for total of 35.147682648084 HMNY
| stealth address | amount | amount idx | tag |
| 00: 06a67e8462c403896a03e74c8f45727af762ebe70613ac02fbb68682535f3c9b | 35.147682648084 | 554 of 0 | <37> |
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": 608,
"vin": [ {
"gen": {
"height": 548
}
}
],
"vout": [ {
"amount": 35147682648084,
"target": {
"tagged_key": {
"key": "06a67e8462c403896a03e74c8f45727af762ebe70613ac02fbb68682535f3c9b",
"view_tag": "37"
}
}
}
],
"extra": [ 1, 185, 205, 153, 235, 93, 214, 73, 220, 126, 7, 249, 118, 18, 71, 185, 98, 178, 96, 225, 26, 56, 131, 225, 189, 88, 14, 251, 1, 125, 250, 45, 84, 2, 9, 0, 0, 0, 8, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}