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: 77b0485561febc494ac84ba241f5e2f7b66f297e7ca5d2c0b1bb02ea9cbeea58
Tx prefix hash: 33e1ae8cd191c8461ce48d3b5328fc94002b451e94872b9fedd59fb56c88b7f5
Tx public key: c01f3785ae58cfcba08f64fdb19a7d610274d89eff768987410204b7ea787029
| Timestamp: 1781006667 | Timestamp [UTC]: 2026-06-09 12:04:27 | Age [y:d:h:m:s]: 00:006:02:48:25 |
| Block: 8563 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 182 | RingCT/type: yes/0 |
| Extra: 01c01f3785ae58cfcba08f64fdb19a7d610274d89eff768987410204b7ea787029020900000001e49593ff00 | ||
1 output(s) for total of 34.614451722607 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1feac8d42b64b220d3220f457a7efac321c6bf78a74d02e7cf6f6bb5c2642159 | 34.614451722607 | 10573 of 0 | <fe> |
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": 8623,
"vin": [ {
"gen": {
"height": 8563
}
}
],
"vout": [ {
"amount": 34614451722607,
"target": {
"tagged_key": {
"key": "1feac8d42b64b220d3220f457a7efac321c6bf78a74d02e7cf6f6bb5c2642159",
"view_tag": "fe"
}
}
}
],
"extra": [ 1, 192, 31, 55, 133, 174, 88, 207, 203, 160, 143, 100, 253, 177, 154, 125, 97, 2, 116, 216, 158, 255, 118, 137, 135, 65, 2, 4, 183, 234, 120, 112, 41, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}