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: 304eae23929caf49fbfbaf82558018fe475020d61449444f16add6b9ef6967fb
Tx prefix hash: 765bbd80f2131afbd058eced5b3ae7dbf66e546df27043fcc61c7018ff9468c3
Tx public key: 861cec1f11ac5a90b43a16dac85e5b064e802c940b12c5e47f3be86e9b4a25ac
| Timestamp: 1781022809 | Timestamp [UTC]: 2026-06-09 16:33:29 | Age [y:d:h:m:s]: 00:006:06:42:03 |
| Block: 8713 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 32 | RingCT/type: yes/0 |
| Extra: 01861cec1f11ac5a90b43a16dac85e5b064e802c940b12c5e47f3be86e9b4a25ac020900000001e49593ff00 | ||
1 output(s) for total of 34.604549855629 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9953fee10c853464ea3e35c3738676c58caa2b2b9667fe20120a1c01f82e1d02 | 34.604549855629 | 10775 of 0 | <8e> |
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": 8773,
"vin": [ {
"gen": {
"height": 8713
}
}
],
"vout": [ {
"amount": 34604549855629,
"target": {
"tagged_key": {
"key": "9953fee10c853464ea3e35c3738676c58caa2b2b9667fe20120a1c01f82e1d02",
"view_tag": "8e"
}
}
}
],
"extra": [ 1, 134, 28, 236, 31, 17, 172, 90, 144, 180, 58, 22, 218, 200, 94, 91, 6, 78, 128, 44, 148, 11, 18, 197, 228, 127, 59, 232, 110, 155, 74, 37, 172, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}