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: 0a3d9b9e245a8e9cc12a6f59cc9dc0eb7aea8490b9190b846e9d7f4394c14428
Tx prefix hash: 6dbe915d11c0d3c00cd4b45c4e4daf81a761e40a546dd078c5855c1c1f03e0a2
Tx public key: f4a7c69296dfbbad5264ce7c7b4d5d1b4538da05e2ebd4b33ca91b86148310f5
| Timestamp: 1780994566 | Timestamp [UTC]: 2026-06-09 08:42:46 | Age [y:d:h:m:s]: 00:004:02:19:30 |
| Block: 8301 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 444 | RingCT/type: yes/0 |
| Extra: 01f4a7c69296dfbbad5264ce7c7b4d5d1b4538da05e2ebd4b33ca91b86148310f5020900000001e49593ff00 | ||
1 output(s) for total of 34.631753780604 HMNY
| stealth address | amount | amount idx | tag |
| 00: dedee03feef77e455da5383bd4446c8601a6022361305555ea071e5065868011 | 34.631753780604 | 10271 of 0 | <96> |
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": 8361,
"vin": [ {
"gen": {
"height": 8301
}
}
],
"vout": [ {
"amount": 34631753780604,
"target": {
"tagged_key": {
"key": "dedee03feef77e455da5383bd4446c8601a6022361305555ea071e5065868011",
"view_tag": "96"
}
}
}
],
"extra": [ 1, 244, 167, 198, 146, 150, 223, 187, 173, 82, 100, 206, 124, 123, 77, 93, 27, 69, 56, 218, 5, 226, 235, 212, 179, 60, 169, 27, 134, 20, 131, 16, 245, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}