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: bf0a9ea343ce7b8e488998ebdd353e3071fbb5fa6ed49700c69eb9bf0fd1fd7d
Tx prefix hash: e406a3e7313e0f6fa7a5f39f30cc46de695f493c9b144d85fde5da82cde83849
Tx public key: 42ec0aa821a37731316ff43ed73db556101c8cc1c4f70c846d39aa1f4c38e819
| Timestamp: 1780313911 | Timestamp [UTC]: 2026-06-01 11:38:31 | Age [y:d:h:m:s]: 00:011:23:23:45 |
| Block: 4992 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3753 | RingCT/type: yes/0 |
| Extra: 0142ec0aa821a37731316ff43ed73db556101c8cc1c4f70c846d39aa1f4c38e81902090000000226697be300 | ||
1 output(s) for total of 34.851020630676 HMNY
| stealth address | amount | amount idx | tag |
| 00: a8fbd9ac0762f6bf1e21b19f8b7166a214b72ffdd20ad8ea0d47a3c354caba04 | 34.851020630676 | 6355 of 0 | <d9> |
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": 5052,
"vin": [ {
"gen": {
"height": 4992
}
}
],
"vout": [ {
"amount": 34851020630676,
"target": {
"tagged_key": {
"key": "a8fbd9ac0762f6bf1e21b19f8b7166a214b72ffdd20ad8ea0d47a3c354caba04",
"view_tag": "d9"
}
}
}
],
"extra": [ 1, 66, 236, 10, 168, 33, 163, 119, 49, 49, 111, 244, 62, 215, 61, 181, 86, 16, 28, 140, 193, 196, 247, 12, 132, 109, 57, 170, 31, 76, 56, 232, 25, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}