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: 75af15f45cba398657dfb59703a49998588c636a4a17808f5cd5677529884ed4
Tx prefix hash: 1a6b57a799fbfd6992fa81b70d623ae8aaf40fbda7e16abc98fada70528c36a0
Tx public key: 64034a1b0868e9c8bf20ac87389c70bae78fa504e57d18d6a1d34629397c421f
| Timestamp: 1779859551 | Timestamp [UTC]: 2026-05-27 05:25:51 | Age [y:d:h:m:s]: 00:012:17:53:02 |
| Block: 2664 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5222 | RingCT/type: yes/0 |
| Extra: 0164034a1b0868e9c8bf20ac87389c70bae78fa504e57d18d6a1d34629397c421f02090000000126697be300 | ||
1 output(s) for total of 35.006114107508 HMNY
| stealth address | amount | amount idx | tag |
| 00: f94e62879bde5410ea987e43e031d8437fa4bd912d687dc9ebf764716eb5cf10 | 35.006114107508 | 3140 of 0 | <85> |
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": 2724,
"vin": [ {
"gen": {
"height": 2664
}
}
],
"vout": [ {
"amount": 35006114107508,
"target": {
"tagged_key": {
"key": "f94e62879bde5410ea987e43e031d8437fa4bd912d687dc9ebf764716eb5cf10",
"view_tag": "85"
}
}
}
],
"extra": [ 1, 100, 3, 74, 27, 8, 104, 233, 200, 191, 32, 172, 135, 56, 156, 112, 186, 231, 143, 165, 4, 229, 125, 24, 214, 161, 211, 70, 41, 57, 124, 66, 31, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}