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: 371ef07e682f42c3142a2b8ff450f4db62cbecd4f339d806dd5f94e42b0359ec
Tx prefix hash: 5c9ee62b6c3e2502b7a89be89e2ed66ab50506fb810180a30b343499f827854a
Tx public key: b6e173f8817b90fcc87b925ff8cbc730386784ba4f2b09b1868fb62ac83c56dd
| Timestamp: 1779716904 | Timestamp [UTC]: 2026-05-25 13:48:24 | Age [y:d:h:m:s]: 00:022:19:26:42 |
| Block: 1666 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7079 | RingCT/type: yes/0 |
| Extra: 01b6e173f8817b90fcc87b925ff8cbc730386784ba4f2b09b1868fb62ac83c56dd020900000002ba6d17be00 | ||
1 output(s) for total of 35.072812958896 HMNY
| stealth address | amount | amount idx | tag |
| 00: a0849ddf3b514de144235804cf9a459061e24b17018cceab3facddcf96f204c6 | 35.072812958896 | 1830 of 0 | <7b> |
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": 1726,
"vin": [ {
"gen": {
"height": 1666
}
}
],
"vout": [ {
"amount": 35072812958896,
"target": {
"tagged_key": {
"key": "a0849ddf3b514de144235804cf9a459061e24b17018cceab3facddcf96f204c6",
"view_tag": "7b"
}
}
}
],
"extra": [ 1, 182, 225, 115, 248, 129, 123, 144, 252, 200, 123, 146, 95, 248, 203, 199, 48, 56, 103, 132, 186, 79, 43, 9, 177, 134, 143, 182, 42, 200, 60, 86, 221, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}