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: 0d59c890529c64682973f371be93dcb8ae03b000c7e91b34a1da3689af11ddbe
Tx prefix hash: 962813ae55805bea392dbad74c9277a7417d2d33d76d65391f009d2bba439727
Tx public key: 491c13707fb12ade9f0d65d41a2a07bd5850b88d359efc9b65043f9aba99bf37
| Timestamp: 1779479674 | Timestamp [UTC]: 2026-05-22 19:54:34 | Age [y:d:h:m:s]: 00:017:06:55:14 |
| Block: 638 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7271 | RingCT/type: yes/0 |
| Extra: 01491c13707fb12ade9f0d65d41a2a07bd5850b88d359efc9b65043f9aba99bf3702090000000593369e7d00 | ||
1 output(s) for total of 35.141649660560 HMNY
| stealth address | amount | amount idx | tag |
| 00: d8ab09750ad5060d5f32a6d883dcf4aadc5f7d1535fe50c1b4c59bdbf8a21eef | 35.141649660560 | 678 of 0 | <82> |
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": 698,
"vin": [ {
"gen": {
"height": 638
}
}
],
"vout": [ {
"amount": 35141649660560,
"target": {
"tagged_key": {
"key": "d8ab09750ad5060d5f32a6d883dcf4aadc5f7d1535fe50c1b4c59bdbf8a21eef",
"view_tag": "82"
}
}
}
],
"extra": [ 1, 73, 28, 19, 112, 127, 177, 42, 222, 159, 13, 101, 212, 26, 42, 7, 189, 88, 80, 184, 141, 53, 158, 252, 155, 101, 4, 63, 154, 186, 153, 191, 55, 2, 9, 0, 0, 0, 5, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}