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: 00da9a0039bfa343a18e3cb2c570d40710882994f90cb680e9be8c97e62f7595
Tx prefix hash: 0c82be39dc9b6bbe9c6d864adfd2acad86c919790650744b91d93f24c910f184
Tx public key: 9bac0c0fbf12c1b44e4641402086f4721d5b405397148feaba7d75fb9c820143
| Timestamp: 1780692644 | Timestamp [UTC]: 2026-06-05 20:50:44 | Age [y:d:h:m:s]: 00:003:06:48:06 |
| Block: 5805 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2141 | RingCT/type: yes/0 |
| Extra: 019bac0c0fbf12c1b44e4641402086f4721d5b405397148feaba7d75fb9c820143020900000001e49593ff00 | ||
1 output(s) for total of 34.797019871949 HMNY
| stealth address | amount | amount idx | tag |
| 00: d24bc6e722128d4ad2dc2c4d9881d7a45e914589d5f605f40d6068eac170dc29 | 34.797019871949 | 7262 of 0 | <30> |
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": 5865,
"vin": [ {
"gen": {
"height": 5805
}
}
],
"vout": [ {
"amount": 34797019871949,
"target": {
"tagged_key": {
"key": "d24bc6e722128d4ad2dc2c4d9881d7a45e914589d5f605f40d6068eac170dc29",
"view_tag": "30"
}
}
}
],
"extra": [ 1, 155, 172, 12, 15, 191, 18, 193, 180, 78, 70, 65, 64, 32, 134, 244, 114, 29, 91, 64, 83, 151, 20, 143, 234, 186, 125, 117, 251, 156, 130, 1, 67, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}