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: 56fc0fb6e48fbed68e15fd42354c550676c79ae3ecf11e1fe4abaccc7797469b
Tx prefix hash: f48230fb306befbef5676645f55c06bc4b409a1b8434d0b73635492e9b5266e7
Tx public key: d0f6afcf81304ed6755e5b02df0148df26a63e76fe6b77eac8b076d583a34569
| Timestamp: 1780041628 | Timestamp [UTC]: 2026-05-29 08:00:28 | Age [y:d:h:m:s]: 00:010:17:35:29 |
| Block: 4296 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3590 | RingCT/type: yes/0 |
| Extra: 01d0f6afcf81304ed6755e5b02df0148df26a63e76fe6b77eac8b076d583a3456902090000000726697be300 | ||
1 output(s) for total of 34.897316637743 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2712ffb2ce9447f34dd50b5d6846fc7dc1e3b8468d0d4f72f1a56e3b175d2a85 | 34.897316637743 | 5368 of 0 | <46> |
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": 4356,
"vin": [ {
"gen": {
"height": 4296
}
}
],
"vout": [ {
"amount": 34897316637743,
"target": {
"tagged_key": {
"key": "2712ffb2ce9447f34dd50b5d6846fc7dc1e3b8468d0d4f72f1a56e3b175d2a85",
"view_tag": "46"
}
}
}
],
"extra": [ 1, 208, 246, 175, 207, 129, 48, 78, 214, 117, 94, 91, 2, 223, 1, 72, 223, 38, 166, 62, 118, 254, 107, 119, 234, 200, 176, 118, 213, 131, 163, 69, 105, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}