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: 674fc2d4d906860c227b910c0de504a39093106ecdd31e7bdc23b956378d7a85
Tx prefix hash: 19ebee12795df8f745c8a60d1415fd9cdb242e19c480303d2176f86033f04146
Tx public key: f6c2d4bf94a2a8db7fdb86514059fc924209321e3baedfe630496229b6dcf6e0
| Timestamp: 1780739818 | Timestamp [UTC]: 2026-06-06 09:56:58 | Age [y:d:h:m:s]: 00:002:11:15:09 |
| Block: 6399 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1487 | RingCT/type: yes/0 |
| Extra: 01f6c2d4bf94a2a8db7fdb86514059fc924209321e3baedfe630496229b6dcf6e0020900000001e49593ff00 | ||
1 output(s) for total of 34.757618350184 HMNY
| stealth address | amount | amount idx | tag |
| 00: c1466c2e9372c10a0dc55be7a3ef9e673f9e055bf1a6600286b767b30aa68258 | 34.757618350184 | 7890 of 0 | <bc> |
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": 6459,
"vin": [ {
"gen": {
"height": 6399
}
}
],
"vout": [ {
"amount": 34757618350184,
"target": {
"tagged_key": {
"key": "c1466c2e9372c10a0dc55be7a3ef9e673f9e055bf1a6600286b767b30aa68258",
"view_tag": "bc"
}
}
}
],
"extra": [ 1, 246, 194, 212, 191, 148, 162, 168, 219, 127, 219, 134, 81, 64, 89, 252, 146, 66, 9, 50, 30, 59, 174, 223, 230, 48, 73, 98, 41, 182, 220, 246, 224, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}