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: 743e9fd7bb18ebb760363ec67621ac82777ab1ebdca717a4c1f90d590eb7adc2
Tx prefix hash: a020c2284a5c1b6842200462d0da6078238db40bf24d1d20cf5edffd4f2f0463
Tx public key: f3accea1a10c67def1d9f27c08f933d4e9523275a9078446873891d93e5f1afb
| Timestamp: 1779946570 | Timestamp [UTC]: 2026-05-28 05:36:10 | Age [y:d:h:m:s]: 00:011:19:59:47 |
| Block: 3567 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4319 | RingCT/type: yes/0 |
| Extra: 01f3accea1a10c67def1d9f27c08f933d4e9523275a9078446873891d93e5f1afb02090000000426697be300 | ||
1 output(s) for total of 34.945873658006 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2d3c36d675a3933cbfe65a16470a2c992a9fb375ce01a10909405808c14d7a9a | 34.945873658006 | 4304 of 0 | <6c> |
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": 3627,
"vin": [ {
"gen": {
"height": 3567
}
}
],
"vout": [ {
"amount": 34945873658006,
"target": {
"tagged_key": {
"key": "2d3c36d675a3933cbfe65a16470a2c992a9fb375ce01a10909405808c14d7a9a",
"view_tag": "6c"
}
}
}
],
"extra": [ 1, 243, 172, 206, 161, 161, 12, 103, 222, 241, 217, 242, 124, 8, 249, 51, 212, 233, 82, 50, 117, 169, 7, 132, 70, 135, 56, 145, 217, 62, 95, 26, 251, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}