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: 407a7210e5f1f2ff9c5570a5858d5d88e603455b872c5e5ae5e25815d023eba1
Tx prefix hash: 11df1e206122c2df4b1e9928307e940b029f34218c84b8621f792fc6a6d2dfba
Tx public key: 11949e8a321270bd380af51b9c3c3791dd6f02429f3b66c3774c7662a50123b6
| Timestamp: 1779878022 | Timestamp [UTC]: 2026-05-27 10:33:42 | Age [y:d:h:m:s]: 00:012:16:16:06 |
| Block: 2911 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5011 | RingCT/type: yes/0 |
| Extra: 0111949e8a321270bd380af51b9c3c3791dd6f02429f3b66c3774c7662a50123b602090000000126697be300 | ||
1 output(s) for total of 34.989626066592 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0fe085fb354f2e4e736c6a03576ddcdd15c25ee6f94106e61093beadc181b796 | 34.989626066592 | 3449 of 0 | <20> |
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": 2971,
"vin": [ {
"gen": {
"height": 2911
}
}
],
"vout": [ {
"amount": 34989626066592,
"target": {
"tagged_key": {
"key": "0fe085fb354f2e4e736c6a03576ddcdd15c25ee6f94106e61093beadc181b796",
"view_tag": "20"
}
}
}
],
"extra": [ 1, 17, 148, 158, 138, 50, 18, 112, 189, 56, 10, 245, 27, 156, 60, 55, 145, 221, 111, 2, 66, 159, 59, 102, 195, 119, 76, 118, 98, 165, 1, 35, 182, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}