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: 7cf779cb777b6b41d98129615cb0ebdb25b31a781875412b0e310362cfd82182
Tx prefix hash: c1a2895a7c364031ff8ef504bd74ac8a71df0ee56c421d95cdf31f0482d02687
Tx public key: 42f08e92f831a4f925ab823d67d6d4370e58b8b8dd70af51446f04c6521f113d
| Timestamp: 1779967069 | Timestamp [UTC]: 2026-05-28 11:17:49 | Age [y:d:h:m:s]: 00:011:14:18:08 |
| Block: 3817 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4069 | RingCT/type: yes/0 |
| Extra: 0142f08e92f831a4f925ab823d67d6d4370e58b8b8dd70af51446f04c6521f113d02090000000b26697be300 | ||
1 output(s) for total of 34.929214123290 HMNY
| stealth address | amount | amount idx | tag |
| 00: 08bc9f4c0efe43da56bc5abe4e397439102ac187448c095693288bf3f8f3c420 | 34.929214123290 | 4646 of 0 | <b6> |
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": 3877,
"vin": [ {
"gen": {
"height": 3817
}
}
],
"vout": [ {
"amount": 34929214123290,
"target": {
"tagged_key": {
"key": "08bc9f4c0efe43da56bc5abe4e397439102ac187448c095693288bf3f8f3c420",
"view_tag": "b6"
}
}
}
],
"extra": [ 1, 66, 240, 142, 146, 248, 49, 164, 249, 37, 171, 130, 61, 103, 214, 212, 55, 14, 88, 184, 184, 221, 112, 175, 81, 68, 111, 4, 198, 82, 31, 17, 61, 2, 9, 0, 0, 0, 11, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}