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: 7650b3c732c420e89495c47a489d0ae53b8411934a7f8b7b98339460a2369774
Tx prefix hash: 4174bbc7be359e0c81035c6b4ee73f4704558971d153552c029e2215204651f6
Tx public key: a5cb66626acf7d708c109e14157f3227c3a1f7932f4dc359b6748cd12da46d53
| Timestamp: 1779435527 | Timestamp [UTC]: 2026-05-22 07:38:47 | Age [y:d:h:m:s]: 00:017:15:40:06 |
| Block: 122 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7764 | RingCT/type: yes/0 |
| Extra: 01a5cb66626acf7d708c109e14157f3227c3a1f7932f4dc359b6748cd12da46d53020900000002a662ed0300 | ||
1 output(s) for total of 35.176252845611 HMNY
| stealth address | amount | amount idx | tag |
| 00: 71777b63aa5e30e612ed4975f7e5a405da7fb47daf2e0fbadcad281c1a2afdb2 | 35.176252845611 | 118 of 0 | <ca> |
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": 182,
"vin": [ {
"gen": {
"height": 122
}
}
],
"vout": [ {
"amount": 35176252845611,
"target": {
"tagged_key": {
"key": "71777b63aa5e30e612ed4975f7e5a405da7fb47daf2e0fbadcad281c1a2afdb2",
"view_tag": "ca"
}
}
}
],
"extra": [ 1, 165, 203, 102, 98, 106, 207, 125, 112, 140, 16, 158, 20, 21, 127, 50, 39, 195, 161, 247, 147, 47, 77, 195, 89, 182, 116, 140, 209, 45, 164, 109, 83, 2, 9, 0, 0, 0, 2, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}