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: 3d587df65b95e114eaa27a51a4fe74040c0d8a310312d64a2f213707befd87f9
Tx prefix hash: 4b65e0b88d50b03c8f5a4a51d93239c27954d2e2bd2ce57b4b66a73e950039fb
Tx public key: a53c4b226018cfa18994532fbb07d5e422aefec46bee22385724f1e5aba2f516
| Timestamp: 1779950211 | Timestamp [UTC]: 2026-05-28 06:36:51 | Age [y:d:h:m:s]: 00:011:18:59:06 |
| Block: 3611 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4275 | RingCT/type: yes/0 |
| Extra: 01a53c4b226018cfa18994532fbb07d5e422aefec46bee22385724f1e5aba2f51602090000000826697be300 | ||
1 output(s) for total of 34.942941003838 HMNY
| stealth address | amount | amount idx | tag |
| 00: a3734ab25cb57b4ed883604322e31e7bf50b1c8f7392b8289c355b122add2703 | 34.942941003838 | 4360 of 0 | <f3> |
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": 3671,
"vin": [ {
"gen": {
"height": 3611
}
}
],
"vout": [ {
"amount": 34942941003838,
"target": {
"tagged_key": {
"key": "a3734ab25cb57b4ed883604322e31e7bf50b1c8f7392b8289c355b122add2703",
"view_tag": "f3"
}
}
}
],
"extra": [ 1, 165, 60, 75, 34, 96, 24, 207, 161, 137, 148, 83, 47, 187, 7, 213, 228, 34, 174, 254, 196, 107, 238, 34, 56, 87, 36, 241, 229, 171, 162, 245, 22, 2, 9, 0, 0, 0, 8, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}