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: a1cf8412464158fcdf9076cfd37479430613251e5d34752a4326d460b3e64875
Tx prefix hash: de8f64f682a2acd47220514569d3534be7a8cd3148523fb27e579cdec270407c
Tx public key: 34ca3cc78e7de7af39b1effa5fc5335bbd29ed50b1703a344f60e2c411c9ea69
| Timestamp: 1780058510 | Timestamp [UTC]: 2026-05-29 12:41:50 | Age [y:d:h:m:s]: 00:010:12:54:07 |
| Block: 4486 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3400 | RingCT/type: yes/0 |
| Extra: 0134ca3cc78e7de7af39b1effa5fc5335bbd29ed50b1703a344f60e2c411c9ea6902090000000326697be300 | ||
1 output(s) for total of 34.884672260616 HMNY
| stealth address | amount | amount idx | tag |
| 00: b8c01a80d5b196560a6dd886fc379c914535b1567eff08fa1290c53a624b9784 | 34.884672260616 | 5622 of 0 | <f3> |
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": 4546,
"vin": [ {
"gen": {
"height": 4486
}
}
],
"vout": [ {
"amount": 34884672260616,
"target": {
"tagged_key": {
"key": "b8c01a80d5b196560a6dd886fc379c914535b1567eff08fa1290c53a624b9784",
"view_tag": "f3"
}
}
}
],
"extra": [ 1, 52, 202, 60, 199, 142, 125, 231, 175, 57, 177, 239, 250, 95, 197, 51, 91, 189, 41, 237, 80, 177, 112, 58, 52, 79, 96, 226, 196, 17, 201, 234, 105, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}