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: bf1d7d7c7cc63ce0fc3c6e2b430cafda8158e806a0625fff29cfa649068001dc
Tx prefix hash: 9882ea8f5b124183e5e0df5cec46acfc807e61dababbb49910174de4a30f8ed9
Tx public key: 340a94217e0248594462aec6c79cefc9473167f106d060d5f83c2e940daca625
| Timestamp: 1779917682 | Timestamp [UTC]: 2026-05-27 21:34:42 | Age [y:d:h:m:s]: 00:018:10:44:53 |
| Block: 3330 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5415 | RingCT/type: yes/0 |
| Extra: 01340a94217e0248594462aec6c79cefc9473167f106d060d5f83c2e940daca62502090000000326697be300 | ||
1 output(s) for total of 34.961674233614 HMNY
| stealth address | amount | amount idx | tag |
| 00: fee0c87d091fe795699d49358042e1773bca909c9602712a7ce6b80f53274bd8 | 34.961674233614 | 4000 of 0 | <10> |
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": 3390,
"vin": [ {
"gen": {
"height": 3330
}
}
],
"vout": [ {
"amount": 34961674233614,
"target": {
"tagged_key": {
"key": "fee0c87d091fe795699d49358042e1773bca909c9602712a7ce6b80f53274bd8",
"view_tag": "10"
}
}
}
],
"extra": [ 1, 52, 10, 148, 33, 126, 2, 72, 89, 68, 98, 174, 198, 199, 156, 239, 201, 71, 49, 103, 241, 6, 208, 96, 213, 248, 60, 46, 148, 13, 172, 166, 37, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}