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: ea6a22e82a7009ac7155c7e1211a8a162c81d100222b0dfa2c87789566f186eb
Tx prefix hash: bfbf9385ec092a773e1640a1e814c61c44b05b574998a427968f4aa26ec01ef3
Tx public key: 0e919587bdd1c11dfd4c5aa0c45c81e9b2567a22a95ab6ce01ade465dd6b7198
| Timestamp: 1780068586 | Timestamp [UTC]: 2026-05-29 15:29:46 | Age [y:d:h:m:s]: 00:010:12:09:04 |
| Block: 4619 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3323 | RingCT/type: yes/0 |
| Extra: 010e919587bdd1c11dfd4c5aa0c45c81e9b2567a22a95ab6ce01ade465dd6b719802090000000126697be300 | ||
1 output(s) for total of 34.880839922688 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2f0c75ea7ce7a4768805f3cd05a218a31e7bb0c561cd1876b972568c073b4de7 | 34.880839922688 | 5798 of 0 | <bc> |
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": 4679,
"vin": [ {
"gen": {
"height": 4619
}
}
],
"vout": [ {
"amount": 34880839922688,
"target": {
"tagged_key": {
"key": "2f0c75ea7ce7a4768805f3cd05a218a31e7bb0c561cd1876b972568c073b4de7",
"view_tag": "bc"
}
}
}
],
"extra": [ 1, 14, 145, 149, 135, 189, 209, 193, 29, 253, 76, 90, 160, 196, 92, 129, 233, 178, 86, 122, 34, 169, 90, 182, 206, 1, 173, 228, 101, 221, 107, 113, 152, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}