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: 12d5ba20ecc37a6c6f621cee18013a803510b732c2b2e062391fd1b118078308
Tx prefix hash: 7085168a04c5ebc75e5384487daad2214abb55625f6028ce2074f3f1138dccae
Tx public key: ea37a925a45341223610be9a734e3526b005fe5ee2ceae60fa8b530d27c1cc47
| Timestamp: 1779641751 | Timestamp [UTC]: 2026-05-24 16:55:51 | Age [y:d:h:m:s]: 00:015:09:53:57 |
| Block: 1359 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6540 | RingCT/type: yes/0 |
| Extra: 01ea37a925a45341223610be9a734e3526b005fe5ee2ceae60fa8b530d27c1cc47020900000001ba6d17be00 | ||
1 output(s) for total of 35.093356089604 HMNY
| stealth address | amount | amount idx | tag |
| 00: 964d32d3e301bd7925d313524ec7d4e85bcaa453ad437d6b41feb6152ff0de7d | 35.093356089604 | 1509 of 0 | <2c> |
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": 1419,
"vin": [ {
"gen": {
"height": 1359
}
}
],
"vout": [ {
"amount": 35093356089604,
"target": {
"tagged_key": {
"key": "964d32d3e301bd7925d313524ec7d4e85bcaa453ad437d6b41feb6152ff0de7d",
"view_tag": "2c"
}
}
}
],
"extra": [ 1, 234, 55, 169, 37, 164, 83, 65, 34, 54, 16, 190, 154, 115, 78, 53, 38, 176, 5, 254, 94, 226, 206, 174, 96, 250, 139, 83, 13, 39, 193, 204, 71, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}