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: 85deb167a77d47774d91192f7835e0138f2ebf99e3875e013c267479c860246f
Tx prefix hash: a923d0f1da3f39528ffb1f1391b4420db37bd3d0bf5578938bab2e90b68bc738
Tx public key: 4f8b8606ec4cc3bf1193dc100377de02a1cdb160f6897a0178247bf92b7648e1
| Timestamp: 1779773224 | Timestamp [UTC]: 2026-05-26 05:27:04 | Age [y:d:h:m:s]: 00:013:20:08:53 |
| Block: 2043 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5843 | RingCT/type: yes/0 |
| Extra: 014f8b8606ec4cc3bf1193dc100377de02a1cdb160f6897a0178247bf92b7648e102090000000126697be300 | ||
1 output(s) for total of 35.047602177247 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1314fca1a8e9dea7df8d559c3c9bf2a90b78db4a58b7afd93bf94de049c913d2 | 35.047602177247 | 2335 of 0 | <e1> |
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": 2103,
"vin": [ {
"gen": {
"height": 2043
}
}
],
"vout": [ {
"amount": 35047602177247,
"target": {
"tagged_key": {
"key": "1314fca1a8e9dea7df8d559c3c9bf2a90b78db4a58b7afd93bf94de049c913d2",
"view_tag": "e1"
}
}
}
],
"extra": [ 1, 79, 139, 134, 6, 236, 76, 195, 191, 17, 147, 220, 16, 3, 119, 222, 2, 161, 205, 177, 96, 246, 137, 122, 1, 120, 36, 123, 249, 43, 118, 72, 225, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}