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: ce38764e848386397eff1042b0751956d639ff2b20238be3e453ea6e99333c57
Tx prefix hash: 27155fab261c758e151434ecba4f996deff56752b76d6350f786da3325922bd2
Tx public key: 9161ae2f96f5be6deb097efc7f63644289dda552f4df3a615d5bdf928f2074b8
| Timestamp: 1779884211 | Timestamp [UTC]: 2026-05-27 12:16:51 | Age [y:d:h:m:s]: 00:012:11:02:02 |
| Block: 2990 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4896 | RingCT/type: yes/0 |
| Extra: 019161ae2f96f5be6deb097efc7f63644289dda552f4df3a615d5bdf928f2074b802090000000226697be300 | ||
1 output(s) for total of 34.984354202939 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7b1aae8afc8eae27216483618a31d3ac0601c5d5df656e815ae5b8b9f67ab9db | 34.984354202939 | 3548 of 0 | <52> |
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": 3050,
"vin": [ {
"gen": {
"height": 2990
}
}
],
"vout": [ {
"amount": 34984354202939,
"target": {
"tagged_key": {
"key": "7b1aae8afc8eae27216483618a31d3ac0601c5d5df656e815ae5b8b9f67ab9db",
"view_tag": "52"
}
}
}
],
"extra": [ 1, 145, 97, 174, 47, 150, 245, 190, 109, 235, 9, 126, 252, 127, 99, 100, 66, 137, 221, 165, 82, 244, 223, 58, 97, 93, 91, 223, 146, 143, 32, 116, 184, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}