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: 708ebae450e59f83eb010d80082a02bd3207f2f39066f020702b04e92fe4c105
Tx prefix hash: c4ec2097b3907fcbc0f82606c6fb997741a0b3fff8380759b4455f6238fa35c1
Tx public key: c6deda6bcabd73febecfc99fc7e56ea17366dc70ef85c0fca32e666a330acc80
| Timestamp: 1780711768 | Timestamp [UTC]: 2026-06-06 02:09:28 | Age [y:d:h:m:s]: 00:002:22:37:19 |
| Block: 6161 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1725 | RingCT/type: yes/0 |
| Extra: 01c6deda6bcabd73febecfc99fc7e56ea17366dc70ef85c0fca32e666a330acc80020900000002e49593ff00 | ||
1 output(s) for total of 34.800031732236 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7a39c80efcf27c6a006d6c0c8eb75c123bb14adb5fc75b0a324f0e6d800403ea | 34.800031732236 | 7636 of 0 | <dc> |
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": 6221,
"vin": [ {
"gen": {
"height": 6161
}
}
],
"vout": [ {
"amount": 34800031732236,
"target": {
"tagged_key": {
"key": "7a39c80efcf27c6a006d6c0c8eb75c123bb14adb5fc75b0a324f0e6d800403ea",
"view_tag": "dc"
}
}
}
],
"extra": [ 1, 198, 222, 218, 107, 202, 189, 115, 254, 190, 207, 201, 159, 199, 229, 110, 161, 115, 102, 220, 112, 239, 133, 192, 252, 163, 46, 102, 106, 51, 10, 204, 128, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}