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: a687c809343a03a1c733f0469b94c2457f581573a5a6c429c6c966617e12ffd0
Tx prefix hash: 0c5093c0b8df27312f1e214f23a1e733627a0ec563bb2b94ee0e157bdf13b083
Tx public key: 5fbc11d430e62f25ce7ecee542512933dc383146a9342ea8347489cdad76967c
| Timestamp: 1780128787 | Timestamp [UTC]: 2026-05-30 08:13:07 | Age [y:d:h:m:s]: 00:009:15:05:46 |
| Block: 4924 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2962 | RingCT/type: yes/0 |
| Extra: 015fbc11d430e62f25ce7ecee542512933dc383146a9342ea8347489cdad76967c02090000000126697be300 | ||
1 output(s) for total of 34.855541095298 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9c28efc4d50e32180dd373581ba90b17f2117d1340fcadfa1d2c05a3a14eafc9 | 34.855541095298 | 6251 of 0 | <9b> |
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": 4984,
"vin": [ {
"gen": {
"height": 4924
}
}
],
"vout": [ {
"amount": 34855541095298,
"target": {
"tagged_key": {
"key": "9c28efc4d50e32180dd373581ba90b17f2117d1340fcadfa1d2c05a3a14eafc9",
"view_tag": "9b"
}
}
}
],
"extra": [ 1, 95, 188, 17, 212, 48, 230, 47, 37, 206, 126, 206, 229, 66, 81, 41, 51, 220, 56, 49, 70, 169, 52, 46, 168, 52, 116, 137, 205, 173, 118, 150, 124, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}