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: cfdf103d8c49f159def371676bf3ab4d147fa79f09d6b0ef061c17384dba7b46
Tx prefix hash: c39e975c4e98d2884888b8b13998edb7461ba8fc74d2e85254871d1a058880ea
Tx public key: eb2d81ad0a26209b7983b32c6d36e7d64be26b36c1766da4a31ea2670687cbea
| Timestamp: 1779957160 | Timestamp [UTC]: 2026-05-28 08:32:40 | Age [y:d:h:m:s]: 00:019:23:56:32 |
| Block: 3711 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5034 | RingCT/type: yes/0 |
| Extra: 01eb2d81ad0a26209b7983b32c6d36e7d64be26b36c1766da4a31ea2670687cbea02090000000426697be300 | ||
1 output(s) for total of 34.936276795977 HMNY
| stealth address | amount | amount idx | tag |
| 00: f6419b56919488123b549c9b4aa592230a1ffb870f290a7595bba9b082a8945f | 34.936276795977 | 4491 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": 3771,
"vin": [ {
"gen": {
"height": 3711
}
}
],
"vout": [ {
"amount": 34936276795977,
"target": {
"tagged_key": {
"key": "f6419b56919488123b549c9b4aa592230a1ffb870f290a7595bba9b082a8945f",
"view_tag": "d9"
}
}
}
],
"extra": [ 1, 235, 45, 129, 173, 10, 38, 32, 155, 121, 131, 179, 44, 109, 54, 231, 214, 75, 226, 107, 54, 193, 118, 109, 164, 163, 30, 162, 103, 6, 135, 203, 234, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}