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: 16461939529ffaaa48af4c679b9ac3b62c70d79f7d039f9eb7608d75377ab511
Tx prefix hash: a0f3a3596f4f30a6e8f780094359a4ce59fcf3b10b402e8eb606d81558f78ab6
Tx public key: 4daaec677372937c9f8ddd578174d08834436fa92d3b7fa6849ac8a24fa3f215
| Timestamp: 1780055711 | Timestamp [UTC]: 2026-05-29 11:55:11 | Age [y:d:h:m:s]: 00:010:13:40:46 |
| Block: 4451 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3435 | RingCT/type: yes/0 |
| Extra: 014daaec677372937c9f8ddd578174d08834436fa92d3b7fa6849ac8a24fa3f21502090000000426697be300 | ||
1 output(s) for total of 34.887001143689 HMNY
| stealth address | amount | amount idx | tag |
| 00: 63ab1ca34b1b12824e0eef27c01710d685e4e7fed93ff3ac35470a0cd3e9b2b7 | 34.887001143689 | 5571 of 0 | <4e> |
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": 4511,
"vin": [ {
"gen": {
"height": 4451
}
}
],
"vout": [ {
"amount": 34887001143689,
"target": {
"tagged_key": {
"key": "63ab1ca34b1b12824e0eef27c01710d685e4e7fed93ff3ac35470a0cd3e9b2b7",
"view_tag": "4e"
}
}
}
],
"extra": [ 1, 77, 170, 236, 103, 115, 114, 147, 124, 159, 141, 221, 87, 129, 116, 208, 136, 52, 67, 111, 169, 45, 59, 127, 166, 132, 154, 200, 162, 79, 163, 242, 21, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}