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: 8dc6ab50cfa8ab6afd9fe0982ab07e779428a99591c1d9409bdcf70192eb0e22
Tx prefix hash: 34999c66b3732b25a7a2b87f754df8e2b6a82e59c56a688912cd47a5fe0573d4
Tx public key: 278bd24ce91fd77c2d942b120e886e7cd31165bc4036a1e56a6b1e12c6d600db
| Timestamp: 1779649172 | Timestamp [UTC]: 2026-05-24 18:59:32 | Age [y:d:h:m:s]: 00:015:04:19:21 |
| Block: 1476 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6410 | RingCT/type: yes/0 |
| Extra: 01278bd24ce91fd77c2d942b120e886e7cd31165bc4036a1e56a6b1e12c6d600db020900000002ba6d17be00 | ||
1 output(s) for total of 35.114378329925 HMNY
| stealth address | amount | amount idx | tag |
| 00: 04f2fe0236569953b9fe9b68bf0fe8bf9a7ff90c41c4ab1a467a5d53f3a8dadb | 35.114378329925 | 1630 of 0 | <17> |
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": 1536,
"vin": [ {
"gen": {
"height": 1476
}
}
],
"vout": [ {
"amount": 35114378329925,
"target": {
"tagged_key": {
"key": "04f2fe0236569953b9fe9b68bf0fe8bf9a7ff90c41c4ab1a467a5d53f3a8dadb",
"view_tag": "17"
}
}
}
],
"extra": [ 1, 39, 139, 210, 76, 233, 31, 215, 124, 45, 148, 43, 18, 14, 136, 110, 124, 211, 17, 101, 188, 64, 54, 161, 229, 106, 107, 30, 18, 198, 214, 0, 219, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}