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: cea3d40beacdf432f817ab894714a8f2c2db9ee4392354990cdae5654169ec91
Tx prefix hash: a27855ed8b38f7927f55c511bd1357b15964fedafe7d2f075bc9a0f70f37f724
Tx public key: b13e37a27a359a3f396846f41939a93d95fb45ca94fd0ee4e7bc11e4c449513c
| Timestamp: 1780065191 | Timestamp [UTC]: 2026-05-29 14:33:11 | Age [y:d:h:m:s]: 00:010:11:02:46 |
| Block: 4575 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3311 | RingCT/type: yes/0 |
| Extra: 01b13e37a27a359a3f396846f41939a93d95fb45ca94fd0ee4e7bc11e4c449513c02090000000326697be300 | ||
1 output(s) for total of 34.878750943924 HMNY
| stealth address | amount | amount idx | tag |
| 00: e0eb1e7f756eb9ee8518362fe5370af6e39dade1bbdba9ea59ddd58ba75cbe34 | 34.878750943924 | 5743 of 0 | <26> |
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": 4635,
"vin": [ {
"gen": {
"height": 4575
}
}
],
"vout": [ {
"amount": 34878750943924,
"target": {
"tagged_key": {
"key": "e0eb1e7f756eb9ee8518362fe5370af6e39dade1bbdba9ea59ddd58ba75cbe34",
"view_tag": "26"
}
}
}
],
"extra": [ 1, 177, 62, 55, 162, 122, 53, 154, 63, 57, 104, 70, 244, 25, 57, 169, 61, 149, 251, 69, 202, 148, 253, 14, 228, 231, 188, 17, 228, 196, 73, 81, 60, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}