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: 16b409a0cbe62a5c38c4fc3824e0b6a8ee3d437b2e5ee15104f95f7f9f6394aa
Tx prefix hash: f2ebc0330746e402f8d5aacf5af11fc28698d65a4f9b0d9f3277c6acd21882a7
Tx public key: 72286458387cb84f5a87d6ef2da6b06607b3de76701a21e1054bbd544e43202d
| Timestamp: 1779864159 | Timestamp [UTC]: 2026-05-27 06:42:39 | Age [y:d:h:m:s]: 00:012:18:04:08 |
| Block: 2721 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5165 | RingCT/type: yes/0 |
| Extra: 0172286458387cb84f5a87d6ef2da6b06607b3de76701a21e1054bbd544e43202d02090000000226697be300 | ||
1 output(s) for total of 35.002308485513 HMNY
| stealth address | amount | amount idx | tag |
| 00: efbfa29dfe5d93b63ae7058b3e6d3336d0860f188c92eb70e5a417d8d9721b71 | 35.002308485513 | 3213 of 0 | <55> |
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": 2781,
"vin": [ {
"gen": {
"height": 2721
}
}
],
"vout": [ {
"amount": 35002308485513,
"target": {
"tagged_key": {
"key": "efbfa29dfe5d93b63ae7058b3e6d3336d0860f188c92eb70e5a417d8d9721b71",
"view_tag": "55"
}
}
}
],
"extra": [ 1, 114, 40, 100, 88, 56, 124, 184, 79, 90, 135, 214, 239, 45, 166, 176, 102, 7, 179, 222, 118, 112, 26, 33, 225, 5, 75, 189, 84, 78, 67, 32, 45, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}