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: ef1e27bd58083b791d00d8bbfb937ab7211f8e0950d76d7686c3bb4e68a98187
Tx prefix hash: 5ce83c155855612c9c6d9e90b10947d580edbe5a1c41bc1edfb590e9d74fbc63
Tx public key: c01554d4e77dab2fc2e51a5af9a1c72a7a7079cb9e6a1855a0b48ce6e0c76433
| Timestamp: 1780974064 | Timestamp [UTC]: 2026-06-09 03:01:04 | Age [y:d:h:m:s]: 00:000:09:32:23 |
| Block: 7912 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 658 | RingCT/type: yes/0 |
| Extra: 01c01554d4e77dab2fc2e51a5af9a1c72a7a7079cb9e6a1855a0b48ce6e0c76433020900000001e49593ff00 | ||
1 output(s) for total of 34.657458668100 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0de0fa9186d580eede079dba52cf207808cac2c67a96b88f1640b344a93ff999 | 34.657458668100 | 9812 of 0 | <05> |
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": 7972,
"vin": [ {
"gen": {
"height": 7912
}
}
],
"vout": [ {
"amount": 34657458668100,
"target": {
"tagged_key": {
"key": "0de0fa9186d580eede079dba52cf207808cac2c67a96b88f1640b344a93ff999",
"view_tag": "05"
}
}
}
],
"extra": [ 1, 192, 21, 84, 212, 231, 125, 171, 47, 194, 229, 26, 90, 249, 161, 199, 42, 122, 112, 121, 203, 158, 106, 24, 85, 160, 180, 140, 230, 224, 199, 100, 51, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}