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: f75c36f17b0be07ff200ada38d957d22f9620fb37e5422a93949b97707a4d827
Tx prefix hash: 6d293ec8118115569a06895f9bc32cdf699f8c0c1536c587b5d61fc8aa73aaae
Tx public key: de81d2270c06a7fc3db057b6515803d2374430ab6848034f6d107a5d59566862
| Timestamp: 1779917072 | Timestamp [UTC]: 2026-05-27 21:24:32 | Age [y:d:h:m:s]: 00:012:05:25:16 |
| Block: 3322 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4578 | RingCT/type: yes/0 |
| Extra: 01de81d2270c06a7fc3db057b6515803d2374430ab6848034f6d107a5d5956686202090000000626697be300 | ||
1 output(s) for total of 34.962207711005 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7bd6a65a2c772fbecb43d9ad7ab8c409a58777a067531888d51a50ccffede3ed | 34.962207711005 | 3990 of 0 | <66> |
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": 3382,
"vin": [ {
"gen": {
"height": 3322
}
}
],
"vout": [ {
"amount": 34962207711005,
"target": {
"tagged_key": {
"key": "7bd6a65a2c772fbecb43d9ad7ab8c409a58777a067531888d51a50ccffede3ed",
"view_tag": "66"
}
}
}
],
"extra": [ 1, 222, 129, 210, 39, 12, 6, 167, 252, 61, 176, 87, 182, 81, 88, 3, 210, 55, 68, 48, 171, 104, 72, 3, 79, 109, 16, 122, 93, 89, 86, 104, 98, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}